Documentation

Coroid as an MCP server

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

Coroid exposes a remote Model Context Protocol server, so an external agent client can manage work in Coroid through the same governed tool registry the chat assistant uses.

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

The endpoint

The MCP server is served 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 is stateless Streamable HTTP. Authenticate with OAuth or a personal access token.

What it deliberately does not expose

The tool registry is governed, and the 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 are getting the ability to manage work — create and inspect tasks, plans and projects — not a remote execution environment. An MCP client cannot use Coroid as a way to run arbitrary commands.

Access tokens

Tokens are created and managed under Access tokens. Like every other credential, they are shown once and never returned afterwards.

Issue one token per client rather than sharing one. Revoking a single client's access is then a contained action rather than an outage for everyone.

Approvals and automation policies

Approvals is a queue of actions waiting for a human. Automation policies decide what needs to be in that queue.

This is the control that matters. An external client acting on your behalf should be able to do routine things freely and consequential things only with a person agreeing. Set the policies before handing a token to anything that runs unattended.

What it is good for

Driving Coroid from where you already work — an editor, an assistant, an internal tool — without switching to the portal. Creating a task from your terminal, or having an assistant check what is blocked, becomes a local action.