Pythe

MCP and API

Use Pythe from Claude, ChatGPT, Cursor or Codex. All 23 MCP tools with their inputs, how sign-in and workspaces work, recipes, the REST gateway and the safety model.

  • 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.
  • Connect your AI app: Step-by-step setup for Claude, ChatGPT, Cursor, Claude Code and Codex, plus the REST fallback for tools that cannot sign in with OAuth.
  • Sign-in, workspaces and permissions: OAuth 2.1 with a consent screen where you pick one workspace. Every call is checked against that binding, and your database row-level security has the final say.
  • AI team tools: Give AI employees tasks, follow each run, answer their questions, stop them, and see what is waiting for approval.
  • Company and plan tools: Read the company profile and live plan, get a brief for the next task, check credits, run cited research, and add or update plan work.
  • Library and memory tools: List, search and read saved work and the team’s memory, and save notes and chats onto a mission card.
  • Recipes: delegate, build, research, keep: Worked patterns for the common jobs: hand work to an AI employee and follow it, build in your own repo from a live brief, run research, and keep what you did in Pythe.
  • Results, polling and errors: AI team tools return a uniform shape with next-step hints and a polling interval, and errors say whether to retry and what to do. Other tools return text with structured content.
  • The REST gateway and API keys: For server-side code, Lovable, n8n and Zapier: call 11 tools with a scoped, expiring, revocable API key. Keys are shown once, stored as hashes, and rate-limited.
  • Protocol notes for developers: What the MCP server tells a client, what the API-key gateway speaks, headers, status codes, and the instructions Pythe gives every connected agent.
  • MCP safety model: No tool can approve. Calls are tied to one workspace, writes reject stale versions, retries are idempotent, saved text is flagged as data, and everything is rate-limited and audited.
  • MCP troubleshooting: Fixes for the usual snags: a 401, an app not bound to a workspace, no plan yet, paused employees, credits, and clients that cached old discovery.