Tokay MCP

Connect an AI agent to Tokay so it can upload code, deploy apps, recover failures, inspect usage, and keep working on the same repository later.

Last updated July 30, 2026

Connect

Add this remote Streamable HTTP endpoint to your MCP client.

https://mcp.tokay.io/mcp

Connecting opens a browser for OAuth approval. You do not paste an API token into the client. Every connection is listed separately under Connected apps and can be disconnected without affecting another installation.

VS Code can use this workspace or user configuration.

{
  "servers": {
    "tokay": {
      "type": "http",
      "url": "https://mcp.tokay.io/mcp"
    }
  }
}

What an agent can do

• Deploy an app from a small inline project or a large repository archive.
• Return later, find the exact repository snapshot, search it, read files, make a conflict safe change, and deploy again.
• Follow Tokay's authoritative deployment readiness instead of guessing from time or logs.
• Resolve configuration, database, source, and release blockers through named tools.
• Diagnose a failed build or deployment with bounded evidence and logs.
• Report current VM capacity and the share used by a Project, Service, or managed database.
• Run a bounded read only query against a managed database when the connection has that permission.
• Use the rest of the public GraphQL surface through a read tool and a fail closed routine mutation tool.

MCP is the workflow surface

MCP carries decisions, metadata, bounded source text, and structured results. It does not carry repository archives, database dumps, or service file bytes through the model context.

Large bytes use short lived capability URLs. The agent asks Tokay for an upload or download URL, transfers the bytes over ordinary HTTP without an OAuth bearer, then continues the workflow with the returned handle. This keeps a large repository faithful without turning it into thousands of tool arguments.

The public GraphQL and REST API remains the full fidelity escape hatch. A client that needs arbitrary API calls should authorize the separate https://api.tokay.io resource and use the API directly. Tokay MCP tokens are accepted only at https://mcp.tokay.io/mcp.

Tokay MCP and an MCP hosted on Tokay

See Deploy an MCP server when the product you are hosting is itself an MCP server.

Permissions

The first connection requests the bundle below. It covers everything from uploading source to recovering a failed deploy.

Logs can contain application data or personal information. Tokay includes PROJECT_LOGS because deployment and recovery are one workflow. Diagnosis returns state and explanation first and includes bounded log bodies only when requested.

Database queries, exports, service file writes, access policy changes, permanent deletion, and other elevated actions stay outside this initial bundle. When a tool needs one, it returns the exact missing PermissionActionType. A new OAuth approval creates another independent connection with the requested union of actions.

Core workflow tools

Platform, safety, and byte tools

The routine mutation policy covers every public GraphQL mutation at server startup. An unknown mutation prevents startup. runServiceTask keeps its documented argv boundary and remains available with PROJECT_INVOKE. Interactive shells, credential minting, VM control, and account operations are either routed to a dedicated reviewed tool or unavailable through MCP.

Reviews and retry safety

Reviewed actions use two calls. The first call returns the exact impact and a ten minute receipt. Repeating the exact request with that receipt consumes it once. A changed request, changed target state, different OAuth connection, expired receipt, or replay fails.

Repository writes and deploys use caller stable idempotency keys where a lost response could duplicate durable work. Retrying the same source or readiness target returns the same repository, commit, or rollout. A diagnosed failed rollout becomes a new retry target and receives exactly one successor rollout under the same workflow key. Reusing the key for different input fails.

Unknown readiness actions and blocker kinds stop safely. An agent must never invent the safety assertion required to recover a maintenance hold.

Privacy and retention

• Tokay validates the live OAuth connection for every MCP request.
• Disconnecting the connection blocks the next tool call and any unused capability URL or queued source side effect.
• Secret values are accepted only by write only tools and are never returned.
• Tokay does not log OAuth bearers, source contents, database query text or results, application log bodies, release commands, capability tokens, or credentials shown once.
• Operational logs may record the tool name, principal and target IDs, support reference, result size, status, and duration.
• Platform OAuth connections expire after 30 days without use. Capability URLs and review receipts expire much sooner and are single use.

Read the privacy policy and security model. Email hello@tokay.io for support.

Troubleshooting