porchops.dev

The developer surface for PorchOps

Two doc families under one roof: bring your own agent (BYOA) over MCP, and author playbooks against OpenPlaybook, the open playbook spec. Everything here is the plain technical register. No marketing, just the wiring.

MCP · BYOAConnect your agentPoint Claude Desktop, Claude Code, Cursor, or any Streamable HTTP MCP client at your PorchOps workspace. Quickstart, tokens, limits, and the generated tool catalog.OpenPlaybookAuthor a playbookOpenPlaybook is the open, JSON-canonical format for structured agentic work. Read the format reference, run the tutorial, and learn how steps declare tools.IntegratorsBuild on the platformVersioning and deprecation policy, the security disclosure contact, and pointers to the public status and changelog surfaces.

The shape of it

A PorchOps API token is a bearer credential (pkk_…) scoped to one workspace. Point any MCP client at a per-server endpoint over Streamable HTTP and pass the token: that is the whole handshake.

mcp client config

{
  "url": "https://mcp-customer-graph.porchops.com/mcp",
  "headers": { "Authorization": "Bearer pkk_yourworkspace_…" }
}

New here? Start with the MCP quickstart, or read how tokens, scopes, and rotation work in the token guide.