Server data from the Official MCP Registry
Keeps AI coding agents on one codebase from overwriting each other, and briefs each on its code.
About
Keeps AI coding agents on one codebase from overwriting each other, and briefs each on its code.
Remote endpoints: streamable-http: https://mcp.corkcli.com
Security Report
Valid MCP server (2 strong, 2 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Found in Source Code
Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-corkcli-mcp": {
"url": "https://mcp.corkcli.com"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
Cork: run multiple AI coding agents on one repo without conflicts
Cork is the coordination layer for multiplayer coding agents: it keeps Claude Code, Codex and Cursor agents, on one machine or across a team's machines, from overwriting each other on one codebase, and hands each agent what the others already learned.
This repository is Cork: run as many coding agents as you like on one machine, in as many repositories as you like, without them tripping over each other. Free, no account, and nothing of yours leaves your machine.
curl -fsSL https://corkcli.com/install.sh | sh
or, with Node (any terminal, including Windows PowerShell):
npx corkcli
One install covers every repository on the machine. Agents already open pick it up at their next prompt.
Or as a plugin. In Claude Code, send these as two separate messages:
/plugin marketplace add corkcli/cork
/plugin install cork@cork
In Codex: codex plugin marketplace add corkcli/cork, then codex plugin add cork@cork. What the plugin brings and does: plugin/README.md.
Why
Run two or three Claude Code agents (or Codex, or Cursor) on the same codebase and they start colliding: one renames a function another is still calling, two write the same module, a push fails and the agent burns turns pulling and re-testing. Each agent also re-reads the same files the others just read. Separate git worktrees keep their files apart, but the work still meets at merge time.
Cork sits under the agents you already run. It does not run agents or host machines. Its hooks tell each agent what the others are changing while they work, hold a write that would clash, and hand each prompt the exact code it is about, so agents search less.
In Cork's benchmark (12 Claude Code agents at once on one repository, hard tasks), agents with Cork used 53% fewer tokens than the same agents without it. The study · all benchmarks
What your agents get
- A briefing before they start. The functions a prompt is about, with their signatures, who calls them and what changed recently, handed to the agent before it searches.
- Each other's work as it happens. When another agent renames a function yours uses, or writes the module your task needs, your agent hears about it on its next step.
- Writes that would clash are held. An edit against code another agent just changed waits until your agent has their version.
- Lint from teammates' changes. A rename or a new signature becomes a rule your agents are checked against.
- One-step pushes.
git pushbrings in the other agents' commits, runs your tests on the result and pushes, instead of the reject, pull, retry loop. - Messages between agents.
cork message "..."reaches the other agents in the repository, or one of them (--to), or whoever is on a piece of code (--about path.py::symbol). - Notes that stay with the code. When an agent finishes a change, what it said about the change is kept on the functions it touched, and the next agent there is handed it.
- MCP tools.
get_symbol,blast_radius,recap,rememberand more, from the same code graph the hooks keep. - What it saved. Once a day your agent's terminal shows the tokens Cork saved on this machine.
How it compares
| Cork | Git worktrees | Agent orchestrators and cloud agents | |
|---|---|---|---|
| Where agents run | Where they already run | Where they already run | On their servers or VMs |
| Agents see each other's changes while working | Yes | No, only at merge | Varies |
| Holds a write that would clash | Yes | No | No |
| Briefs each agent on the code its prompt is about | Yes | No | Varies |
| Works with Claude Code, Codex and Cursor together | Yes | Yes | Varies |
They combine: agents in separate worktrees still benefit from Cork telling them what the others are changing. Detailed comparisons: corkcli.com/blog/compare.
Commands
| Command | What it does |
|---|---|
cork status | What Cork did on this machine, and where its data is |
cork message "..." | Tell the other agents in this repository something |
cork agents-md | Add Cork's section to this repository's AGENTS.md, after what is already there |
cork login | Link this machine to a Cork account |
cork upgrade | Units for your workspace: 100 agent hours a month each, pooled |
cork uninstall | Take Cork's hooks out (your local data stays) |
Where your data is
Everything stays in ~/.cork/local (~/.collide/local on a machine set up before the rename) on your machine: a small server on 127.0.0.1 that only this machine can reach. Cork makes no calls out, except to check for a signed update of itself.
Other machines, and a team
Free and local, Cork connects the agents on one machine. cork login signs the machine in to Cloud Free (10 agent hours a month): it moves to Cork's servers with nothing else to download, brings its history along, and your agents on your other signed-in machines see its work. Cork's paid plan ($20 a month per 100 agent hours, pooled across the workspace) adds your teammates: their agents see your agents' work, and prompts are matched to code by meaning, not only by the names they use. cork upgrade opens the billing page for units.
Frequently asked questions
How do I run multiple Claude Code agents on the same repo without conflicts?
Install Cork (one command above), then start your agents as usual. Each agent hears what the others are changing, a write against code another agent is changing is held until it has their version, and git push rebases, tests and pushes in one step. Guide: run multiple Claude Code agents on one repo.
Does it work with Codex and Cursor? Yes. The install registers Cork's hooks for Claude Code, Codex and Cursor, and its MCP server for any MCP client.
Is Cork an MCP server?
It is both hooks and an MCP server. The hooks do the work with no extra model calls; the MCP server adds tools an agent can call on purpose. The hosted server is https://mcp.corkcli.com.
Does my code leave my machine?
Not when it runs free and local. Signed in, on Cloud Free or the paid plan, your source files still don't: the hooks parse each file on your machine and send its structure (names, signatures, docstrings, who calls what, a hash per line). cork audit shows every request, and What Cork sends lists them all.
Is it really free? Yes: free with no account and no time limit, for one machine.
Build from source
cd free && cargo build --release
./target/release/cork install
free/ builds the one program, cork: the hooks your agents run (hooks/, with the parser in core/) and the local server (cork local). AGENTS.md is the guide for working on this code, for people and agents alike; Claude Code, Codex, Cursor and Windsurf each find their own config for it here.
Skills for agents
Cork's official agent skills are in skills/: setting Cork up, working with its briefings and write gate, handing work off and messaging other agents, and reading what Cork recorded. Install them for any agent that reads skills:
npx skills add corkcli/cork
Documentation
- Setup by tool: Claude Code · Codex · Cursor · Gemini CLI
- Reference: the
corkcommand · MCP tools · all docs - Guides: Do you need git worktrees for AI coding agents? · Cleaning up the worktrees agents leave behind
- Changelog · Benchmarks · For agents: llms.txt, agents.md
What is in this repository
| Folder | What it is | License |
|---|---|---|
hooks/ | What runs in your agent sessions: briefings, the write gate, landing, messages, the MCP bridge, install | MIT |
core/ | The code parser and graph the hooks and the engine share | MIT |
free/ | The engine: the local server that keeps the map, the briefings, lint, landing and memory | FSL-1.1-MIT |
protocol/ | The real-time protocol the hooks speak: spec, schema, engine, domains, a reference server and a TypeScript client | MIT |
plugin/ | The Claude Code and Codex plugin | MIT |
skills/ | Cork's official agent skills | MIT |
The engine's license lets you use, change and share it for anything except offering a competing product or service; each version becomes MIT two years after its release.
If Cork saved your agents a merge conflict, a star helps other developers running parallel agents find it. Questions and ideas: open an issue. Website: corkcli.com · Claude Code plugin: corkcli/cork
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
