Question 1

What is the PitHub MCP server?

Accepted Answer

It is a small server that lets any MCP client, Claude, Cursor, Codex, Gemini and others, publish conversations to PitHub without leaving your agent.

Once connected, you can say things like “push this to PitHub”, “add this to that pit” or “search PitHub for prompts about X”, and the agent calls the matching tool. The server is a thin client over the same public REST API the web app uses.

Question 2

How do I install the MCP server?

Accepted Answer

There are two ways in, with the same tools. Remote points your client straight at pithub.app/mcp with nothing to install. npm runs the pithub-mcp package locally over stdio.

The docs page has a tailored config snippet for each supported agent, pick your agent and paste it where that agent keeps its MCP servers.

Question 3

Which tools does the MCP server expose?

Accepted Answer

The full set covers the pit lifecycle: create_pit, append_to_pit, update_pit, publish_pit, get_pit, list_my_pits, search_pits, fork_pit and delete_pit. list_teams and list_team_pits provide team workspace access.

There are also preview_pit_selection to see which messages would be published before publishing, collaboration tools like add_collaborator and list_collaborators, and list_pit_versions to read a pit's full push history.

For the files a pit carries (skill files, prompts, playbooks), add_pit_files attaches them, list_pit_files lists them, and get_pit_file reads their text back, either one named file or all of them at once.

Question 4

Is there a REST API I can call directly?

Accepted Answer

Yes. The MCP server is a thin client over a public REST API, so you can build against it directly. Authenticate with an Authorization: Bearer <token> header.

Endpoints cover pits (create, read, update, delete, fork, like, bookmark, export), the feed, Explore, users and the current account. Create a token in Settings and it is scoped to your account and revocable at any time.