PluginBench
MCP Server
Active

agentsync MCP Server

io.github.jarmstrong158/agentsync

What is the agentsync MCP server?

Multi-agent coordination MCP: claim work, survey peers, resolve conflicts via a git branch as CAS.

How to install agentsync

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • AGENTSYNC_REPO

    Absolute path to the shared project git clone used for coordination.

  • AGENTSYNC_AGENT_ID

    Your unique agent id, used to key your claims.

  • AGENTSYNC_BRANCH

    The dedicated coordination branch (default: agentsync).

~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agentsync": {
      "command": "uvx",
      "args": [
        "agentsync-mcp"
      ],
      "env": {
        "AGENTSYNC_REPO": "<YOUR_AGENTSYNC_REPO>",
        "AGENTSYNC_AGENT_ID": "<YOUR_AGENTSYNC_AGENT_ID>",
        "AGENTSYNC_BRANCH": "<YOUR_AGENTSYNC_BRANCH>"
      }
    }
  }
}

Related MCP servers

Cloudflare Worker remote transport for agentsync. MCP 2026-07-28, dual-era, stateless.

1
TypeScript
MIT
View repository →
CACambium logo

Cambium

Active

Knowledge-lifecycle MCP: turn agent work into memory, recall it across projects, promote to org.

0
Python
View repository →

Cloudflare Worker for read-only recall of cambium knowledge. MCP 2026-07-28, dual-era.

0
TypeScript
MIT
View repository →

Durable project-memory MCP: decisions, constraints, and pipelines across Claude sessions.

1
Python
MIT
View repository →

Cloudflare Worker remote backend for context-keeper (D1). MCP 2026-07-28, dual-era.

0
TypeScript
MIT
View repository →

Job search and ranking pipeline via MCP for Claude Desktop.

2
Python
MIT
View repository →