COTAL actions (cotal.ai)

What COTAL actions (cotal.ai) does

COTAL actions (cotal.ai) connects an MCP client to selected functions of the Cotal website and build log. It combines read operations for product and documentation discovery with write operations for feedback, subscriptions, requests, and editorial content.

The cotal_overview tool returns structured information about Cotal, including its purpose, intended users, installation approach, API and MCP surface, pricing, and canonical links. Its optional section argument narrows the response to one part of that overview.

The server also provides access to the Cotal build log. Agents can search posts and key site pages, list posts in reverse chronological order, and fetch an individual post as markdown by slug. Search results include canonical and markdown URLs, while post listings include metadata such as title, summary, date, author, slug, and pagination information.

How it works

Search is intended to locate the relevant page before an agent reads it. cotal_list_posts supports cursor pagination; the returned cursor can be passed to retrieve the next page. cotal_get_post uses a slug obtained from search or listing results.

Several tools submit information to Cotal. Feedback is categorized as a bug, idea, friction, praise, or other report and requires the user's email for follow-up. Waitlist enrollment for Cotal Cloud is idempotent per email, so repeating the request updates optional details rather than creating another seat. Newsletter subscription is also idempotent.

Editorial tools follow a review workflow. A draft post starts as a draft, can be sent for review as pending, and only goes live after human publication. Updates create a new revision when the title, dek, or body changes. A base revision can be supplied to prevent an update from overwriting a newer revision.

Setup and configuration

Connect the server through an MCP client and provide the inputs required by each action. Feedback and waitlist operations use an email address; a newsletter subscription also uses an email address. A discovery-call request requires a work email and company.

The post drafting, updating, listing, and retrieval tools for staged articles require a team key on the MCP connection. The draft and update operations return or use revision information so editorial changes can be tracked safely.

Tools and capabilities

• Return a structured Cotal product and API overview.
• Search Cotal documentation, site pages, and build-log posts.
• Browse paginated posts and retrieve full posts as markdown.
• Submit categorized feedback and request a founder discovery call.
• Join the Cotal Cloud waitlist or subscribe to release updates.
• Draft, revise, inspect, and review staged build-log articles.

Limitations and notes

Editorial changes do not publish immediately. New drafts require human publication before appearing live, and revisions to published posts remain separate from the live text until publication. Team-key-protected tools are unavailable without that credential on the connection. Requests that involve follow-up depend on the email address supplied by the user.