MCP.so
Sign In

Agent Coherence MCP Server

@Cohexa

Basic information

Category

Files & Storage

License

NOASSERTION

Author

Cohexa

Submitted by

Cohexa

About Agent Coherence MCP Server

Stop AI agents from silently overwriting each other's shared files — a single-host coherence guard, TLA+-verified.

Agent Coherence MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "stale-write-guard-fs": {
      "command": "uvx",
      "args": [
        "--from",
        "agent-coherence[mcp]",
        "stale-write-guard-fs"
      ]
    }
  }
}

Agent Coherence MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is agent-coherence?

A coherence guard for shared files: when two agents (or sessions) write the same artifact, the stale writer is denied instead of silently overwriting — then reacquires and retries. Same protocol across LangGraph, CrewAI, AutoGen, the OpenAI Agents SDK, plain files (CoherentVolume), and any MCP client (stale-write-guard-fs).

How to use it

MCP: pip install "agent-coherence[mcp]", then run stale-write-guard-fs. Library: pip install agent-coherence and use CoherentVolume, or the CCSStore LangGraph drop-in.

Key features

  • MESI single-writer ownership + invalidation — a stale write is denied fail-closed
  • Optimistic commit-CAS for concurrent same-key writers
  • Read-generation fence for crash-reclaimed writers
  • Five safety invariants machine-checked in TLA+ (make tla-check in CI)
  • MCP server (5 tools), LangGraph/CrewAI/AutoGen adapters, Claude Code plugin

Honest scope

Single-host today: concurrent same-key writers on one host are covered; cross-host fencing is on the roadmap, demand-gated.

Comments

More Files & Storage MCP servers