Coordigent
Coordinates AI coding agents working in parallel on a shared GitHub repo, enabling them to message one another, see shared file state, and receive warnings when their work overlaps another agent's edits.
Coordigent
Coordigent is an MCP server for teams running more than one AI coding agent on the same repository. It shares which files each agent is working in, warns when two sessions overlap, and lets agents message one another — so parallel work stops ending in silent overwrites.
coordis the installed binary.
Coordigent lets agents message one another, see shared file state across a team, and receive warnings when their work overlaps another agent's edits. Teams can coordinate contributions to one existing repo while keeping the tools they already use. Coordigent also provides a directory where agents discover tools and capabilities.
The hosted instance runs at coordigent.com. This repository holds the public documentation for installing Coordigent and connecting it to your coding client; it does not contain the Coordigent source.
What Coordigent does
Two coding agents on one repository cannot see each other. Each has its own context window and its own working copy, and neither knows what the other has touched. The failure is quiet: both edit the same file from different starting points, and the last write wins. You find out at merge, or later.
Git resolves the merge. What git does not do is tell an agent, while it is still deciding what to edit, that another agent is in that file right now. Coordigent does that.
Shared file state — every connected agent reports the files it is working in, so any agent can ask what the rest of the team currently has open instead of inferring it from the last commit.
File-conflict warnings — when one agent's work overlaps a file another agent is already in, Coordigent raises a warning. Warnings arrive as banners on the result of whatever tool the agent just called, so they reach every client rather than only the ones that implement optional MCP capabilities, and they stay readable in
coordigent.message.inbox.Agent-to-agent messaging —
coordigent.message.sendandcoordigent.message.inbox, addressed between sessions. This is how an agent hands off work, asks another to hold off on a file, or reports that a shared interface changed.One repository, many agents — built around a single existing GitHub repository, not around isolating each agent. Nothing is migrated.
Directory — agents discover tools and capabilities through
coordigent.directory.search.
Coordigent does not host your code, merge it, run your CI, or replace review. Your repository stays on GitHub with the history and permissions it already has. Full detail in docs/how-it-works.md.
Related MCP server: asynkor
Install
One line per machine. It downloads coord and coord-mcp into ~/.tower/bin, signs the machine in with your own token, and registers Coordigent with every supported client it finds:
curl -fsSL https://coordigent.com/install.sh | sh -s -- --token <your-token>macOS and Linux. Windows is untested — see the FAQ.
Get a command with your token already filled in at coordigent.com/install. Then verify with:
coord doctorSupported clients
Client | Connect with | Guide |
Cursor |
| |
Codex |
| |
Claude Code |
| |
VS Code / Copilot |
| |
Kiro |
| |
Windsurf / Cascade |
| |
Perplexity |
|
Any other MCP client works through coord install generic, which writes a plain mcp.json you point the client at.
Coordigent is model-agnostic. Every client runs the same stdio MCP server, coord-mcp, and no client config ever holds a token — credentials live in ~/.tower/config.json.
Pricing
Solo: free.
Team: $20 USD per seat per month. Team pricing is currently a preview; paid billing is not yet available.
Documentation
How it works — the pieces, and what Coordigent deliberately does not do.
Command line reference — every
coordandcoordigentcommand, and the full MCP tool surface an agent sees.Comparisons — MCP Agent Mail, Agent Orchestration, Wormhole, Raft, Buzz, Entire, Cursor Origin. Sourced and dated; corrections welcome as issues.
Install guides: Cursor · Codex · Claude Code · VS Code · Kiro · Windsurf · Perplexity
More
Documentation in this repository is licensed under CC BY 4.0. The coord binary and the Coordigent service are not covered by that license.
This server cannot be deployed
Maintenance
Related MCP Connectors
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Shared memory and actions for Claude, Kiro, OpenAI, Cursor, and other MCP-compatible AI clients.
One shared context your team's AI tools read & write over MCP. No re-explaining. Free.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server for coordinating parallel AI coding sessions with tools like Claude Code and Codex in a single repository.2MIT
- AlicenseNot gradedqualityDmaintenanceCoordination layer for AI coding agents working on the same codebase. Adds file locks, shared project memory, and cross-machine file sync so Claude Code, Cursor, Windsurf, and other MCP agents stop overwriting each other.50Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.44 npm8MIT
- AlicenseAqualityBmaintenanceEnables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.52 npmMIT