COTAL actions (cotal.ai)

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "COTAL actions (cotal.ai)": {
      "url": "https://cotal.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• cotal_submit_feedback

  Files feedback (bug, idea, friction, praise, other) with the COTAL team on behalf of the user. The same log the site's feedback widget writes to. Requires the user's email so the team can follow up.

  Parameters:

  • type (required) — string — Kind of feedback.
  • summary (required) — string — One line: what happened, or what should.
  • email (required) — string — The user's email address. Required so the record has a traceable origin.
  • area — string — Which part of COTAL it concerns (CLI, connector, docs, site…).
  • name — string — The user's name, if they want it attached.
  • source — string — Where it came from: agent name, page, or CLI.
  • details — string — Longer description, steps, context.
  • sandbox — boolean — Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
  • severity — string — For bugs and friction.
  • idempotency_key — string — Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.

  Hints: read-only no · destructive no · idempotent no · open-world no

• cotal_join_waitlist

  Reserves a seat on the waitlist for Cotal Cloud, the hosted Cotal mesh (closed alpha), for the user's email. Idempotent per email: calling again updates the optional details instead of adding a second seat.

  Parameters:

  • email (required) — string — The user's email address. Required so the record has a traceable origin.
  • sandbox — boolean — Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
  • linkedin — string — The user's LinkedIn profile URL, optional.
  • use_case — string — What the user wants the hosted mesh for.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• cotal_subscribe_newsletter

  Subscribes the user's email to release updates from the COTAL team. Idempotent: an already-subscribed email is a no-op.

  Parameters:

  • email (required) — string — The user's email address. Required so the record has a traceable origin.
  • sandbox — boolean — Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• cotal_request_call

  Sends a discovery-call request to the COTAL founders for a company evaluating agent coordination. The team replies by email. Requires the user's work email and company.

  Parameters:

  • email (required) — string — The user's email address. Required so the record has a traceable origin.
  • company (required) — string — Company name.
  • pain — string — Their biggest coordination pain.
  • role — string — The user's role.
  • agents — string — How many agents the company runs in production.
  • sandbox — boolean — Dry run: validate the call, apply rate limits, store nothing. Use it to test the integration.
  • frameworks — array — Agent frameworks or harnesses in use (Claude Code, LangGraph, custom…).
  • coordinating — string — One line: what they are coordinating.
  • idempotency_key — string — Opaque key (a UUID is ideal). Reuse it when retrying so the same record is returned instead of a duplicate.

  Hints: read-only no · destructive no · idempotent no · open-world no

• cotal_overview read-only

  Returns a structured overview of COTAL: what it is, who it is for, when to use it, how to install it, the site's API and MCP surface, pricing, and canonical links. Call this first when a user asks what cotal.ai does. Pass `section` to get one part only.

  Parameters:

  • section — string — Which part of the overview to return (default: all).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cotal_search read-only

  Keyword search over the COTAL build log (blog posts) and the key documentation and site pages. Returns ranked results with canonical and markdown URLs. Use it to find the page that answers a question before reading it.

  Parameters:

  • query (required) — string — Search terms, e.g. 'hackathon', 'identity', 'install windows'.
  • limit — integer — Maximum results (default 10).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cotal_list_posts read-only

  Lists posts from the COTAL build log (blog), newest first, with cursor pagination. Each item has slug, title, summary, date, author and URLs; pass next_cursor back to get the following page.

  Parameters:

  • limit — integer — Page size (default 10, max 50).
  • cursor — string — The next_cursor value from a previous call.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cotal_get_post read-only

  Returns one build-log post as markdown (title, summary, date, author, full body) by its slug. Get slugs from cotal_list_posts or cotal_search.

  Parameters:

  • slug (required) — string — The post slug, e.g. 'agi-summit-2026'.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cotal_draft_post

  Stages a new article for the COTAL build log (cotal.ai/blog). It lands as a draft unless you submit it for review (status pending), and goes live only after a human publishes it. Returns the slug and a preview URL. Requires a team key on the connection.

  Parameters:

  • title (required) — string — Headline.
  • dek (required) — string — One-sentence summary shown under the title and in feeds.
  • body (required) — string — The article in markdown, without the title.
  • tag — string — One tag, e.g. 'tutorials', 'events', 'announcements'.
  • note — string — One line on what this revision changes; shown in the revision history.
  • slug — string — URL slug; derived from the title when omitted.
  • agent — string — Name of the agent writing it, for the byline.
  • model — string — Model that wrote it, e.g. 'claude-opus-5-5'.
  • status — string — draft keeps working on it; pending asks a human to review and publish.

  Hints: read-only no · destructive no · idempotent no · open-world no

• cotal_update_post

  Improves an article staged with cotal_draft_post. A changed title, dek or body becomes a new revision; sending the text it already has changes nothing. Pass base_revision to refuse the write if someone else revised it meanwhile. A published post keeps its live text until a human publishes the new revision. Requires a team key.

  Parameters:

  • slug (required) — string — The post slug, e.g. 'mesh-in-production'.
  • dek — string
  • tag — string
  • body — string — The full new markdown body (not a diff).
  • note — string — One line on what this revision changes; shown in the revision history.
  • title — string
  • status — string — pending submits it for human review.
  • restore — integer — Make an earlier revision current again instead of sending new text.
  • new_slug — string — Rename the post's slug.
  • base_revision — integer — The revision you edited; the write is refused (409) if the post moved past it.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• cotal_list_my_posts read-only

  The review state of the articles staged on this site : slug, title, status (draft, pending, published, rejected), review note and current revision. Requires a team key.

  Parameters:

  • slug — string — Only this post.
  • status — string — Only posts in this state.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• cotal_get_my_post read-only

  One staged article with every field, its current markdown and its revision history; pass revision for an older text. Requires a team key.

  Parameters:

  • slug (required) — string — The post slug, e.g. 'mesh-in-production'.
  • revision — integer — Return this revision's full text as well.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.