ali8hsn

Coordigent — AI skill for Claude Code

AI community

Coordigent: an MCP server for teams running more than one AI coding agent on the same repository.

How to install Coordigent

This entry records only its repository, not the path inside it, so there is no exact command to give. Open ali8hsn/coordigent and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Coordigent does

Coordigent: an MCP server for teams running more than one AI coding agent on the same repository. Shares file state, warns on overlaps, and lets agents message one another. Public docs for installing coord and connecting Cursor, Codex, Claude Code, VS Code, Kiro, Windsurf and Perplexity.

Alternatives in AI

Hexstrike AI — HexStrike AI MCP Agents is an advanced MCP server that lets AI agents (Claude, GPT, Copilot, etc.) autonomousl 8.2k ★
Agent Teams AI — You're the boss, agents are your team 2k ★
CLI Continues — resume any AI coding session in another tool — Claude Code, Copilot, Gemini, Codex, Cursor 1.5k ★

README

Coordigent

[![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/trycrews-com-install)

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. `coord` is 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](https://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 capa