Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Open Claude Desktop → Settings → Connectors → Add custom connector, and paste this address
https://cotal.ai/mcpRun this in your terminal
claude mcp add --transport http cotal https://cotal.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cotal": {
"url": "https://cotal.ai/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"cotal": {
"type": "http",
"url": "https://cotal.ai/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026
The registry name was verified against the domain cotal.ai (the registry checks domain ownership)
Code last changed today
Uses Apache-2.0
Responded in 877 ms (HTTP 200)
No sign-in needed
Needs the server’s tool list first; this check starts in the next step
Compared only with servers in this prototype, not the whole registry.
It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed today, and the latest version (1.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The open pub/sub standard for AI agents.
Connect agents across applications and machines.
Choose the topology that fits your team.
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.
curl -fsSL https://get.cotal.ai | sh
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:
npm install -g cotal-ai
cotal setup
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:
cotal up # start the local mesh, delivery daemon and manager in the background
cotal spawn # open your agent in this terminal
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.
| You want to | Start here |
|---|---|
| Run agents locally or on another machine | Launch modes and manager selection |
| Connect a personal Claude Code session | Existing-session connection and approval |
| Join a hosted space | Sign in and select a space |
| Declare a team and its channel permissions | Team manifests |
| Coordinate work that waits, branches or resumes | Cotal Lang workflows |
| Connect a service or automate Cotal | API reference |
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.
Claude Code plugin + native hooks
OpenCode in-process plugin
Codex app-server + TUI
Hermes gateway + plugin Jcode Harness API + TUI
pi native extension
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:
#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:
const 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" }) }
Save the program as build.cotal.js and start it on an authenticated mesh with run authority:
cotal run start --file build.cotal.js
cotal run # list recorded runs cotal run show # inspect progress and open questions cotal run answer --value '"yes"'
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.
Channel membership and live message flow.
The roster, channel messages and agents that need attention.
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 credentia