Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.
Connect Runs on your machine
claude mcp add agentsync -e AGENTSYNC_REPO=<AGENTSYNC_REPO> -e AGENTSYNC_AGENT_ID=<AGENTSYNC_AGENT_ID> -e AGENTSYNC_BRANCH=<AGENTSYNC_BRANCH> -- uvx agentsync-mcp==0.2.0
{
"mcpServers": {
"agentsync": {
"command": "uvx",
"args": [
"agentsync-mcp==0.2.0"
],
"env": {
"AGENTSYNC_REPO": "<AGENTSYNC_REPO>",
"AGENTSYNC_AGENT_ID": "<AGENTSYNC_AGENT_ID>",
"AGENTSYNC_BRANCH": "<AGENTSYNC_BRANCH>"
}
}
}
}
{
"mcpServers": {
"agentsync": {
"command": "uvx",
"args": [
"agentsync-mcp==0.2.0"
],
"env": {
"AGENTSYNC_REPO": "<AGENTSYNC_REPO>",
"AGENTSYNC_AGENT_ID": "<AGENTSYNC_AGENT_ID>",
"AGENTSYNC_BRANCH": "<AGENTSYNC_BRANCH>"
}
}
}
}
{
"servers": {
"agentsync": {
"type": "stdio",
"command": "uvx",
"args": [
"agentsync-mcp==0.2.0"
],
"env": {
"AGENTSYNC_REPO": "<AGENTSYNC_REPO>",
"AGENTSYNC_AGENT_ID": "<AGENTSYNC_AGENT_ID>",
"AGENTSYNC_BRANCH": "<AGENTSYNC_BRANCH>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
AGENTSYNC_REPOOptional | Absolute path to the shared project git clone used for coordination. |
AGENTSYNC_AGENT_IDOptional | Your unique agent id, used to key your claims. |
AGENTSYNC_BRANCHOptional | The dedicated coordination branch (default: agentsync). |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 2 Aug 2026 |
| Last updated | 2 Aug 2026 |
| Registry name | io.github.jarmstrong158/agentsync |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
