COTAL actions (cotal.ai)

What it does

This is the hosted MCP endpoint of the cotal.ai website, run by the COTAL team. It is not the Cotal agent mesh itself (the open pub/sub standard in the linked GitHub repository); it is a small server for asking about that product and contacting the people behind it. The server's own instructions say that to put an agent on a Cotal mesh you should not use this server but follow docs.cotal.ai/prompt.md instead.

It has 12 tools in version 1.1.0, per its server card (the GitHub README does not list them). Four are open lookups: a structured product overview that can return one section only, a keyword search over the build log and key site pages (10 results by default, up to 25 with `limit`), a paged list of build-log posts (10 per page by default, up to 50) and a single post as markdown. Four act on the user's behalf and create records for the COTAL team: filing feedback, joining the Cotal Cloud waitlist (a closed alpha), subscribing to release updates and requesting a discovery call. Each takes `sandbox=true` to check a call without storing it, and feedback and call requests take an `idempotency_key` so a retry does not duplicate a record.

The last four tools draft, revise and inspect build-log articles, and work only with a COTAL team key on the connection; they stage text, and a person on the team publishes every post. The endpoint also exposes two resources, the site's llms.txt and its OpenAPI spec.

What it needs

An MCP client that speaks Streamable HTTP to https://cotal.ai/mcp. Lookup and intake tools need no account or credential. The four build-log authoring tools need a COTAL team key (ctk_…, made in the site's admin Settings) sent as an Authorization: Bearer header; keys are for the COTAL team and its agents only.

Limits

The action tools (feedback, waitlist, newsletter, call request) are rate limited per client to 5 calls per 10 minutes, per the server's instructions. Without a team key the authoring tools answer 401. Search is keyword search over the build log and a set of key documentation and site pages, not the whole docs site or the web. Drafted posts are never published by the server; a human publishes them. It does not join, run or inspect a Cotal mesh.

Who it suits

Suits someone evaluating COTAL who wants their assistant to answer what it is, find the build-log post or page on a topic, or send feedback, a waitlist request or a call request without filling in web forms. It is hosted by the vendor and needs no setup for those uses. Anyone who wants agents to coordinate over Cotal should install the Cotal mesh itself (cotal-ai on npm) rather than this server, as its own instructions say. The authoring tools are only useful to the COTAL team.