MCP · OpenAPI · Skills
TOSE and MCP
The TOSE MCP server is live at https://app.tose.sh/mcp (Streamable HTTP). Add it to your MCP client, sign in to TOSE and approve the requested scopes: the client handles OAuth 2.1 with PKCE and registers itself, so no API key is needed. Your agent then gets 8 tools to inspect projects, deployments, logs and incidents, deploy and roll back.
Status
| MCP connector Available | Remote MCP server at https://app.tose.sh/mcp with 8 tools: 6 read-only and 2 that change a deployment. | Available |
|---|---|---|
| One-click connect and OAuth for agents Available | OAuth 2.1 with PKCE and dynamic client registration: sign in to TOSE and approve; no API key to copy. | Available |
| Skills inside an MCP client Coming soon | The MCP tools do not include the skills. Read the public Skills catalogue or install a skill with the CLI. | Coming soon |
| OpenAPI description of the TOSE API Available | Public file served by the production API, see below. | Available |
| Public Skills catalogue Available | Public JSON list of agent instructions, see below. It is a document, not an MCP server. | Available |
Connect
- Add a remote (HTTP) MCP server with the URL https://app.tose.sh/mcp in your MCP client.
- Sign in to TOSE in the browser window the client opens and approve the requested scopes.
- Your agent can now call the TOSE tools below, limited to the scopes you approved.
Claude Code:
claude mcp add --transport http tose https://app.tose.sh/mcpOther clients (Claude Desktop, Cursor, Codex and others): add a remote or HTTP MCP server with the same URL. MCP setup guide on docs.tose.sh
Read-only tools
list_projectsget_deployment_statusinspect_deploymentread_logslist_incidentsinspect_incident
Tools that change a deployment (need write scopes)
deploy_projectrollback_deployment
Scopes
workspace:readprojects:readdeployments:readlogs:readdeployments:writedeployments:executedeployments:rollback
Three different things
- MCP connector Available: a server an MCP client connects to with OAuth, at https://app.tose.sh/mcp.
- Skills catalogue and OpenAPI Available: plain public documents you can read or download; no sign-in and no connection to your account.
- WebMCP Coming soon: read-only tools a web page offers to an agent in the browser. It needs an experimental browser flag and is switched off on this site; it is not the MCP server and not a connection point.
Public API documents
Both are public and served by the production API.
- OpenAPI 3.1 description of the user API
- Skills catalogue (JSON): debug-failed-deployment, deploy-nextjs-to-tose, deploy-go-service-to-tose, optimize-cloud-cost, safe-rollback
API keys go in the X-API-Key header, never in a URL. A key can carry scopes; a request outside them fails with insufficient_scope.
Alternative: the CLI with an API key
Claude Code, Codex, Cursor and other agents that run terminal commands can also use the TOSE CLI. Every command accepts --json and returns a result the agent can read. The key is read from TOSE_API_KEY, so it never has to appear in the conversation.
npm install -g @tosesh/tose
tose whoami --json
tose deploy my-workspace/my-app --json
tose status my-workspace/my-app --json
tose logs my-workspace/my-app -n 100Updates
Changes to the MCP server and its tools are listed in the changelog. Changelog