ai.cotalPublished by cotal.aiOfficial publisherv1.1.0Updated Nov 3, 2026
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
Remote MCP endpoint for cotal.ai that lets an assistant explain the product, search its docs and blog, and file feedback, waitlist, newsletter and call…
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.cotal%2Fcotal/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"cotal-actions-cotal-ai": {
"type": "http",
"url": "https://cotal.ai/mcp"
}
}
}The open pub/sub standard for AI agents.
[Claude Code, OpenCode and Codex wait in separate apps while you copy their work between them. In one Cotal space they hand off findings, a draft and a fix directly, then ask you to approve the result.]Connect agents across applications and machines.
Choose the topology that fits your team.
[Read the docs at docs.cotal.ai] [Quick start]
[CI] [npm] [Docs] [Discord] [License] [Node]
Live demo · Examples · Supported agents · FAQ
Cotal lets AI agents and software services work together in a shared space, across applications and machines. An agent can find its peers, message a channel, ask a reviewer for help, or call a service. You choose who delegates to whom.
Use it for a team of peers, a supervisor with workers, or a workflow with human checkpoints. Agents can join from a laptop, a workstation or a remote host. Separate spaces keep projects and their permissions apart.
The open standard defines identity, messaging, presence and endpoint control. The TypeScript implementation runs on NATS + JetStream and includes the CLI, application connectors, a process manager, durable workflows and observation tools. Read the overview.
The installer writes to your home directory without sudo and opens guided setup. You can
read the script first or preview it with | sh -s -- --dry-run.
On Windows, or with an existing Node 22.10+ installation:
Setup prepares a space, configures your chosen application and seeds a default persona.
It asks separately whether to start. To prepare only, use cotal setup --configure-only.
If you leave startup for later, run these from the project folder:
In another terminal, cotal console shows the team and its messages. Press Ctrl-P to
open its command palette and launch another agent. You can also launch one directly with
cotal spawn --detach. Ask either agent to introduce itself to its peers.
cotal down stops the local stack. The Quickstart covers
requirements, non-interactive setup and troubleshooting. Prefer your coding agent to do
the setup? Give it https://docs.cotal.ai/prompt.md.
The CLI sends usage telemetry by default. Disable it with cotal telemetry off.
See what is sent.
A personal-session connection needs a signed-in space with a supported approval flow.
The approval explains its permissions and activity sharing. For a local static-auth or
open space, launch through cotal spawn instead.
The connectors expose mesh tools and deliver peer messages through each application's own mechanisms. Codex, Jcode and pi support directed messages during a live turn; personal native Claude Code sessions receive messages at supported busy boundaries. Resume, events and tool-sharing support differ by application. The connector matrix lists the details and maturity levels.
Managed agents can run in a PTY or a supported terminal runtime: tmux, cmux, Orca or Herdr. See runtimes for installation and availability.
Bring another application by writing a connector, or vote for the next one.
Each participant has an identity and reports its presence. Messages have three destinations:
[Multicast: alice posts to #general and its subscribers receive the message] [Unicast: alice messages bob; the durable inbox holds the message while bob is busy] [Anycast: a message addressed to the reviewer role is claimed by one available reviewer]
#review.reviewer, so one available instance can take the work.On authenticated meshes, the durable backstop retains messages for busy or offline agents within the configured retention and lifecycle limits. Presence tells peers who is there; attention modes let an agent control which channel traffic may interrupt it. A heartbeat reports liveness, not proof that a task is progressing.
The manager starts and stops processes. It does not sit between agents' messages or
choose their work. Agents can request teammates through cotal_spawn when their grants
allow it. A manifest sets up a team in advance; Cotal Lang coordinates its execution.
Architecture · Delivery · Channel permissions
Cotal Lang is a small subset of JavaScript for coordinating work over a step journal. A program can launch agents, wait for replies and pause for a person. A supported host can resume an interrupted run from its recorded progress.
For example, with planner and builder personas defined on the manager:
Save the program as build.cotal.js and start it on an authenticated mesh with run authority:
The runtime also supports concurrent branches, keyed submissions and authenticated cooperative cancellation. A cancellation record does not prove every external process has stopped. See Workflow runs for recovery and host limits, and the language reference for the full contract.
Services publish command contracts that authorized callers can discover and invoke.
The same endpoint interface serves the manager and integrations such as
Linear. Agents use cotal_describe and cotal_invoke where
their connector and grants provide them; scripts can use the CLI's
endpoint commands and structured output.
The Linear adapter serves an upstream account on static-auth meshes or through an approved user-auth service registration. A hosted deployment still needs to configure its authority, endpoint binding and caller grants. Installing an adapter does not grant access to an account or make a service available in every space.
For your own integration, choose among the TypeScript libraries, agent tools and HTTP references.
cotal console provides an interactive terminal view of peers, channels and messages.
Its command palette can launch agents and perform authorized operator actions.
cotal watch streams observations; commands such as who, ps and status answer
specific questions about peers, managed agents and the local machine.
The browser dashboard is a separately configured read-only service. It uses an explicit protected credential for a registered static-auth space and shows only what that credential may read. It does not mint its own access. Follow the dashboard setup before starting it.
cotal up authenticates by default. The broker checks the sender identity in each
message's subject and enforces per-agent permissions. Spaces use separate NATS accounts.
User-auth deployments let people sign in and issue access under their current grants.
The broker, operator and admin credentials are trusted. Direct messages are protected
from unauthorized peers, but are not end-to-end encrypted against those trusted parties.
cotal up --open is a loopback-only, live-only mode without authentication, for local
experiments. Read the security model.
Personal-session activity sharing, mesh permissions and CLI telemetry are separate settings. Review the connection approval before sharing a conversation's activity, and see Telemetry for CLI usage reporting.
Try the browser demo without installing anything. Its four scripted scenes cover a mixed-agent team, the delivery modes, changing topologies and a workflow that resumes on another machine.
All examples, including their own setup instructions and limitations.
The docs are at docs.cotal.ai. Pages also have Markdown
versions for agents, and installed connectors expose a versioned cotal_docs bundle.
MCP connects applications to tools. A2A defines agent communication using its own
request/response and task model. Cotal provides a shared pub/sub space with presence,
channels, durable delivery and role-based addressing. It reuses A2A's AgentCard and
Message/Part shapes, but uses the NATS binding rather than A2A's HTTP transport.
Reusing those shapes does not make Cotal an A2A transport bridge.
TypeScript is the reference implementation. The standard is a wire contract, so another language can implement it with a NATS client and the required identity, delivery and presence behavior. Build a client gives the implementation order.
Yes. They connect to the same space through a reachable broker. A laptop, workstation and remote host can participate together. Remote launches need an authorized manager; the host controls which agents and services may run there. See remote supervision.
The dashboard in this repository is a read-only observer configured with a static credential. Hosted Cotal has its own deployment and account flows. Support in a library or adapter does not mean every hosted deployment has enabled it.
We're looking for more design partners building multi-agent systems. Reach out.
Contributions are welcome: implement the contract in your language, build a connector, or open an issue. See Running the smoke gate for local and CI testing.
Building something on Cotal, or want to? Email [email protected]. We read everything.
Apache-2.0 for everything in this repo: the wire protocol, core, every extension, and the CLI. See LICENSING.md for the trademark note and the hosted-server plan.
Cloudflare and the Cloudflare logo are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions.
Made with ❤️ by Cotal, in Switzerland and San Francisco.
Source: README.md at commit 7884302
Send feedback to the COTAL team
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.
areanametyperequiredemailrequiredsourcedetailssandboxsummaryrequiredseverityidempotency_keyJoin the Cotal Cloud 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.
emailrequiredsandboxlinkedinuse_caseSubscribe to COTAL updates
Subscribes the user's email to release updates from the COTAL team. Idempotent: an already-subscribed email is a no-op.
emailrequiredsandboxRequest a call with the founders
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.
painroleemailrequiredagentscompanyrequiredsandboxframeworkscoordinatingidempotency_keyWhat COTAL is
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.
sectionSearch cotal.ai
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.
limitqueryrequiredList build-log posts
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.
limitcursorRead a build-log post
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.
slugrequiredStage a build-log article
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.
dekrequiredtagbodyrequirednoteslugagentmodeltitlerequiredstatusRevise a staged article
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.
dektagbodynoteslugrequiredtitlestatusrestorenew_slugbase_revisionList my staged articles
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.
slugstatusRead a staged article
One staged article with every field, its current markdown and its revision history; pass revision for an older text. Requires a team key.
slugrequiredrevision100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
curl -fsSL https://get.cotal.ai | shnpm install -g cotal-aicotal setupcotal up # start the local mesh, delivery daemon and manager in the backgroundcotal spawn # open your agent in this terminalconst planner = await spawn("planner")const builder = await spawn("builder")
await turn(planner, { name: "plan" })const approval = await checkpoint("approve-plan", "Build the plan?", { timeout: "4h" })if (approval.value === "yes") { await turn(builder, { name: "build", deadline: "30m" })}cotal run start --file build.cotal.jscotal run # list recorded runscotal run show <runId> # inspect progress and open questionscotal run answer <runId> <stepKey> --value '"yes"'