MCP

Connect your agent to Platform without installing the Zeroshot CLI.

Connect and authorize

The Zeroshot plugins bundle shared run, planning, and graph-design skills for ChatGPT/Codex and Claude. Install the matching package from the Zeroshot repository, then authorize your Platform account. A direct MCP connection also works with the tools below.

Add this remote Streamable HTTP server in an MCP client with OAuth support:

MCP server URL

https://api.app.zeroshot.sh/mcp

Claude Code

claude mcp add --transport http --scope user zeroshot https://api.app.zeroshot.sh/mcp
claude mcp login zeroshot

Sign in in the browser, select your organization, and approve the connection. Keep the approval page open until control returns to the client. Use the API host for MCP; the app host handles browser approval. Other deployments use their API origin followed by /mcp.

Start and follow work

`Profiles`	list_profiles, get_profile, save_profile, validate_profile, and get_authoring_catalog.
`Connections`	list_connections, check_connection, and GitHub browser setup links.
`Environments`	list_environments, get_environment, save_environment, and repository assignments.
`Runs`	submit_profile_run, get_run, wait_for_run, read_run_logs, stop_run, and recovery operations.
`Memory`	list_memory_lessons, get_memory_lesson, update_memory_lesson, and delete_memory_lesson.

Ask the agent to inspect a saved profile, confirm the repository and exact commit, then submit using submit_profile_run. For example: “Run org:default on acme/project at this commit to add a health endpoint.” Provider credentials must already exist in Connections; MCP sign-in does not supply them. Configure provider keys in Platform; the MCP tools accept named connection requirements and never ask you to paste credentials into chat.

Keep the run ID and a stable submissionKey for retries. Follow status with wait_for_run and read_run_logs, using their returned cursors. Wait returns within 30 seconds; timeout or client disconnect leaves the run running. Stop and workspace discard require your intent.

Permissions and automation

MCP uses your existing organization permissions. Environment and Memory writes require the workspace identity from get_authoring_catalog and the current revision when updating. For resume_run, supply a new UUIDv7 in successorRunId; reuse that ID and checkpoint selection when retrying.

Clients that support bearer credentials can use an API key delegation. Machine keys cannot access Memory or manage delegations. MCP has no billing, member-management, or infrastructure tools.