Documentation

Coroid as an MCP server

Drive Coroid from your own assistant or editor via a remote MCP endpoint.

Coroid provides a remote Model Context Protocol server, enabling an external agent client to manage work in Coroid through the same governed tool registry used by the chat assistant.

Configure it under Settings → Automation → Coroid MCP server, which covers Overview, Client setup, Access tokens, Approvals and Automation policies.

The endpoint

The MCP server is hosted by the API gateway:

https://api.coroid.ai/mcp
EnvironmentEndpoint
Productionhttps://api.coroid.ai/mcp
Staginghttps://staging-api.coroid.ai/mcp
Developmenthttp://localhost:3000/mcp

The transport protocol is stateless Streamable HTTP. Authenticate using OAuth or a personal access token.

What it deliberately does not expose

The tool registry is governed, and these exclusions are intentional. It does not provide:

  • a shell
  • Git access
  • the filesystem
  • raw database access
  • arbitrary internal HTTP
  • Coroid's own outbound MCP administration tools

You gain the ability to manage work — create and inspect tasks, plans and projects — not a remote execution environment. An MCP client cannot use Coroid to run arbitrary commands.

Access tokens

Tokens are created and managed under Access tokens. Like all other credentials, they are displayed once and never shown again.

Issue one token per client instead of sharing a single token. Revoking a client's access then affects only that client rather than causing an outage for everyone.

Approvals and automation policies

Approvals form a queue of actions awaiting human approval. Automation policies determine what gets placed in that queue.

This is the crucial control mechanism. An external client acting on your behalf should be able to perform routine tasks freely while requiring human agreement for consequential actions. Set these policies before granting a token to any unattended process.

What it is good for

Using Coroid from your existing workspace — an editor, an assistant, or an internal tool — without needing to switch to the portal. Creating a task from your terminal or having an assistant check pending items becomes a local operation.