How do I install the agent mcp server?

Use a recorded configuration for your client, replace example credential values and paths, and verify the documented runtime. Restart or reconnect the client, then inspect the available tools.

What credentials does it need?

It reads `SWG_ROOT` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

SSyncDev

Start a project

Agent MCP Server — Cohexa-ai/agent-coherence

Vendor-neutral MESI + optimistic-concurrency coordinator for multi-agent state — a stale write is denied or returned as a typed conflict, never

Local serverstdioPython

What is the Agent MCP Server?

Vendor-neutral MESI + optimistic-concurrency coordinator for multi-agent state — a stale write is denied or returned as a typed conflict, never silently applied

The short version

Two agents share an artifact — a plan.md, a store key, a memory.json. One reads it and works; meanwhile a peer commits a newer version; the first writes back anyway. Last write wins, the peer's work is silently gone, nothing errors, and every downstream decision builds on the wrong version. agent-coherence turns that silent clobber into a loud, typed refusal: MESI-style ownership and invalidation over shared artifacts, optimistic commit-CAS for concurrent writers, and a read-generation fence for crash-reclaimed ones — a stale write is denied or returned as a retryable conflict, never silently applied. Same

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
swg_read	Tracked read — registers the agent's view of the file
swg_write	Guarded write — a stale view or a foreign edit gets a typed stale_view deny with recover: reacquire, never a silent overwrite
swg_reacquire	Recovery — fresh identity + mandatory fresh read after a deny
swg_write_cas	Single-shot version-checked write for concurrent same-key contention
swg_status	Three-state coordination health: on / off / unknown

Configuration

Variable	Description	Required
SWG_ROOT	Configuration value read at startup.	Optional

Example prompts to try

“Use Agent to Workload.”
“Use Agent to swg read.”
“Use Agent to swg write.”

Frequently asked questions

Vendor-neutral MESI + optimistic-concurrency coordinator for multi-agent state — a stale write is denied or returned as a typed conflict, never silently applied Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.