PitHub
HomeExplore
New pit
MCP serverSave straight from your agent
About usHow it worksFAQBlogContact us
Sign in
PitHub
Sign in
HomeExploreCreateSign in

Docs · MCP server

Connect PitHub to your AI tools

PitHub's MCP server gives ChatGPT, Claude, Cursor, Codex, and other AI clients a secure way to save, update, find, and share conversations for you.

MCP in plain language

Think of MCP as a bridge between your AI app and PitHub. Once connected, you can ask your AI to save a useful exchange in normal language, no copying, exporting, or reformatting the conversation yourself.

  1. 1ConnectChoose your AI app and add PitHub.
  2. 2AuthorizeApprove access in your browser.
  3. 3AskTell your AI what you want saved.
On this page
1. Connect2. Authorize3. Save your first pitChoose which messagesTools and examplesPlugins and directoriesPublish imagesREST API

Step 1

Choose how to connect

Pick your AI app below and follow its exact setup instructions. Use the remote URL when it is available; it is the simplest option and requires no local installation. The npm package is for coding agents and desktop apps that connect over stdio.

Not sure which to pick? Start with Remote URL. If your app does not support it, the installer will point you to the npm option.

https://pithub.app/mcp

Add just the URL and your client opens a browser to sign in, no token to manage. Clients without that popup can send a Bearer token header instead.

In the ChatGPT app or on chatgpt.com, add PitHub as a connector, a browser opens to sign in, no token to paste. Works for tool calls in chat and as a Deep Research source.

Settings → Connectors
https://pithub.app/mcp

Tip, Settings → Connectors → Add custom connector (turn on Developer mode / connectors if you don't see it), paste the URL, and Authorize. Needs a ChatGPT plan that supports connectors.

Step 2

Authorize your PitHub account

Authorization links the AI client to your account. Your password is never shared with the client, and you can revoke access at any time.

Using the remote URL

The client opens PitHub in your browser. Sign in, choose Authorize, then return to the client. There is no token to copy.

Using the npm package

Ask your agent to “connect to PitHub.” It calls connect_pithub and opens the same browser approval flow.

pithub.app/mcp/authorize

Claude Code wants to connect to your PitHub account

Signed in as @mirakhan

  • Save new pits and new versions
  • Read your pits, including private ones
  • Push to team workspaces you belong to
Code from your clientQK7M-3PDA
DenyAuthorize
The page your client opens in the browser. You are signing in to PitHub, not handing the client a password, and the grant can be revoked from Settings at any time.

Prefer to start the npm sign-in from a terminal?

npx pithub-mcp login

You can also create a token manually in Settings and send it as an Authorization: Bearer header.

Step 3

Save your first pit

You do not need to remember tool names. Ask in normal language and your AI client chooses the right PitHub tool.

Try this
“Save the last exchange to PitHub as ‘MCP onboarding notes’ and keep it private.”
  • Your AI previews or selects the messages you requested.
  • PitHub saves the pit with your title and visibility.
  • The client confirms what was saved and gives you a link.
Claude · pithub connected

Save the last exchange to PitHub as “MCP onboarding notes” and keep it private.

create_pittool call
title:
"MCP onboarding notes"
visibility:
"private"
messages:
[ the last 2 messages ]
Claude

Saved “MCP onboarding notes”.

pithub.app/p/8kq2ndv4t1ac

Private · v1 · 2 messages · only you can see it.

One sentence becomes one tool call. You never type a tool name or an argument, the client fills those in from what you asked, then reports the link it got back.

Everyday use

Choose which messages to save

You rarely need the entire transcript. Describe the part you want, and the server maps your request to a precise, predictable selection. Pick a phrase below to see exactly which messages it saves.

Your conversation, 6 messagessaved messages highlighted
  1. 1How should I structure the onboarding email sequence?
  2. 2Three emails: welcome, first win, then the invite to upgrade.
  3. 3Make the second one shorter and lead with the win.
  4. 4Here it is at 90 words, with the win in the opening line.
  5. 5Good. Now write subject lines for all three.context
  6. 61. You're in. 2. Your first win in ninety seconds. 3. Ready for more?

preview_pit_selection →

Saving 2 of 6 messages · #5, #6. Message #5 comes along as context so the reply still makes sense.

When you select an AI reply, PitHub includes the question above it by default so the answer keeps its context. Say “just the reply” if you only want the answer.

Reference

Tools and example requests

Natural-language requests are usually all you need. These examples show common workflows; the reference below lists every tool available to the client.

Save

“Save this whole conversation to my PitHub and keep it private.”

Share with a team

“Push the last four messages to the platform team as ‘API launch notes’.”

Create a new version

“Append this exchange to my API launch pit.”

Find and reuse

“Find the public onboarding pit and fork it into my account.”

Cursor · pithub connected

Push the last four messages to the platform team as “API launch notes”.

create_pittool call
title:
"API launch notes"
team_slug:
"platform"
messages:
[ the last 4 messages ]
Claude

Saved to the Platform workspace.

pithub.app/p/w0r9xk2mheq5

Visible to 6 membersNot public

Naming a team routes the same create_pit call to that workspace. Team pits are private to current members, so there is no visibility to choose.
ChatGPT · pithub connected

Find the public onboarding pit and fork it into my account.

search_pitstool call
query:
"onboarding"
  • Onboarding email sequence, third pass@mirakhan · 22 likes
  • Onboarding checklist for new agents@dan · 9 likes
fork_pittool call
pit_id:
"jr4t57f36xzf"
Claude

Forked into your account as v1.

pithub.app/p/2vd8slc61pna

Credited to @mirakhan, edit it freely from here.

Finding and reusing is the same shape: one tool searches public pits, another copies one into your account. The fork keeps a link back to the original.

Full tool reference

Save and update

create_pit

Save a new conversation, personally or to a team. Can attach files.

preview_pit_selection

Preview exactly which messages will be saved.

append_to_pit

Add messages as a new version of an existing pit.

update_pit

Change metadata, visibility, or the conversation.

publish_pit

Change a private or unlisted pit to public.

Find and reuse

get_pit

Read a pit and its full conversation.

list_my_pits

List your pits, including private ones.

search_pits

Search public pits.

fork_pit

Copy someone else’s pit into your account.

list_pit_versions

Read the version history of a pit.

Files

add_pit_files

Attach text files to a pit, skills, prompts, playbooks.

list_pit_files

List the files attached to a pit.

get_pit_file

Read the text of a pit’s attached files.

Teams and collaborators

list_teams

List your team workspaces and role in each.

list_team_pits

List the private pits in a team workspace.

add_collaborator

Let another user push to one of your pits.

list_collaborators

See who can push to a pit.

Connection and account

connect_pithub

Open the browser approval page (npm only).

check_connection

Show the connected PitHub account.

delete_pit

Delete one of your own pits.

Distribution

Plugins and directories

Beyond adding the URL by hand, PitHub ships as a Claude Code plugin. Directory listings that need an application are marked pending below.

Claude Code plugin

Installs the hosted server and its OAuth flow in one step. The marketplace lives in the PitHub repo, so it needs no approval from anyone.

/plugin marketplace add homersimpcode/pithub
/plugin install pithub@pithub

The plugin points at the hosted server, which has no filesystem. To attach files from your own disk, add the npm server instead:

claude mcp add pithub -- npx -y pithub-mcp

Where you can install PitHub

live

Remote MCP URL

https://pithub.app/mcp, works in any client that speaks MCP over HTTP.

live

npm package

pithub-mcp on npm, for stdio clients and local file attachments.

live

Claude Code plugin

Self-hosted marketplace in this repo, no approval needed.

pending

Anthropic connector directory

Application required. The OAuth discovery chain it depends on is already in place.

pending

ChatGPT app directory

Submission required. The search and fetch tools it depends on are already implemented.

pending

MCP registry

Submission required, the community index of MCP servers.

Optional

Publish images with a conversation

Generated images can travel with the conversation. How you provide the image depends on the connection type.

npm package

Pass an absolute PNG, JPEG, GIF, WebP, or SVG file path. PitHub uploads it and stores a stable hosted URL.

Remote URL

The hosted server cannot read your computer. Pass a public HTTP(S) URL or a base64 image data URI instead.

images: [{
  source: "/absolute/path/to/generated-poster.png",
  alt: "A glowing archive of saved AI conversations"
}]

By default, the image attaches to the final selected message. Add a 1-based message_index to place it on a different message.

pithub.app · the saved pit
AI · message 4

Here is the poster in the flat, high-contrast style you asked for.

alt: “A glowing archive of saved AI conversations”

An image passed with the save is uploaded once and rehosted by PitHub, then shown under the message it belongs to. The alt text you provide is what readers and search engines get.

Advanced

Use the REST API directly

The MCP server uses the same public REST API. Authenticate requests with Authorization: Bearer <token>.

Pits

POST /api/pits
GET /api/pits/:id
PATCH /api/pits/:id
DELETE /api/pits/:id
POST /api/pits/:id/fork
POST /api/pits/:id/like
POST /api/pits/:id/bookmark
GET /api/pits/:id/export

Discovery and accounts

GET /api/feed
GET /api/explore
GET /api/users/:username
GET /api/teams
POST /api/teams
GET /api/teams/:slug
POST /api/teams/:slug/members
GET /api/me

Export formats: ?format=md|json|txt|prompt

Manage tokensBrowse pits

On this page

  1. Overview
  2. 1. Connect
  3. 2. Authorize
  4. 3. Save your first pit
  5. Choose which messages
  6. Tools and examples
  7. Plugins and directories
  8. Publish images
  9. REST API

Need to reconnect?

Manage or revoke access tokens