The Pythe MCP server
A remote MCP server with 23 tools. Your own agent reads your company, hands tasks to Pythe’s AI employees, follows their runs and reads their reports. It cannot approve anything.
Updated 2026-10-13
Pythe runs a remote MCP server at https://pythe.app/mcp (Streamable HTTP, OAuth 2.1). It works with Claude, ChatGPT, Cursor, Codex and any client that supports remote MCP with OAuth. Connecting works on every plan, including Free. Handing tasks to AI employees needs Base or Premium, where the employees live.
The tools at a glance
| Group | Tools | What they are for |
|---|---|---|
| The AI team | list_team, assign_task, list_runs, get_run, answer_run, cancel_run | Give work to AI employees and follow it. |
| Approvals | list_approvals | See what is waiting. The founder decides in Pythe. |
| Library and memory | list_artifacts, search_library, get_library_item, list_memory, save_note, save_chat | Everything the team saved, searchable. |
| Company and plan | list_workspaces, set_active_workspace, get_founder_context, get_operating_plan, get_plan_build, get_task_prompt, get_credit_balance, run_research, add_milestone, update_operating_plan | The live context behind every answer. |
23 tools in all. Each has an effect, shown on its reference card: Reads, Saves to Pythe, Does work, uses credits or Changes the plan.
What you can do
- Delegate. Give a Researcher, Writer, Engineer, Analyst, Outreach or Operator a brief and follow the run. See Delegate and follow.
- Ground your own agent. Read the live company profile and plan before it writes a line, so its output is on-strategy.
- Get a brief and do the work yourself.
get_task_promptturns the next plan task into a research, build or write brief your client carries out with its own tools, then saves the result back withsave_note. - Keep a record.
save_noteandsave_chatput work and conversations on the mission card in Pythe. - Search what the team knows. The Library and the team’s memory are searchable.
What it will not do
- There is no tool that approves an action. Emails, Slack posts, Notion pages, CRM records, pull requests and website publishes wait for the founder in Pythe.
- There is no tool to hire or fire an employee, change a plan, or start a plan build. The founder does those in Pythe.
- It does not give a client an unattended computer after its conversation ends. Run state lives in Pythe, so you can come back and read it.
Two interfaces, deliberately separate
| MCP server | REST gateway | |
|---|---|---|
| URL | https://pythe.app/mcp | https://pythe.app/api/cofounder |
| Auth | OAuth 2.1, sign in once | A scoped pk_live_… API key |
| For | Claude, ChatGPT, Cursor, Codex and compatible clients | Server-side code, Lovable, n8n, Zapier, and clients without OAuth MCP |
| Tools | 23 (this reference) | 11 (see REST gateway) |
Machine-readable description
The same tool list, with each tool’s effect, is published as an MCP server card at /.well-known/mcp/server-card.json. The tool names and count on the landing page, the /pythe-mcp-server page, the server card and this reference all come from one catalogue file, and a test keeps that catalogue equal to the tools the server really registers.