Enagrams MCP Server

Shared agent memory for co-coding teams. When two developers work on the same codebase with their own AI coding agents, Enagrams gives those agents shared context — decisions, conflict detection, and meeting notes.

Setup

1. Get your API key

Sign up at enagrams.com, create a workspace, and copy your API key.

2. Add to your MCP config

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "enagrams": {
      "command": "npx",
      "args": ["-y", "enagrams-mcp"],
      "env": {
        "ENAGRAMS_API_KEY": "ek_...",
        "ENAGRAMS_WORKSPACE": "my-startup"
      }
    }
  }
}

Claude Code (.mcp.json in your repo root):

{
  "mcpServers": {
    "enagrams": {
      "command": "npx",
      "args": ["-y", "enagrams-mcp"],
      "env": {
        "ENAGRAMS_API_KEY": "ek_...",
        "ENAGRAMS_WORKSPACE": "my-startup"
      }
    }
  }
}

3. Start coding

Both agents will automatically share decisions and detect conflicts.

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | ENAGRAMS_API_KEY | Yes | Your API key from enagrams.com | | ENAGRAMS_WORKSPACE | Yes | Workspace slug or ID | | ENAGRAMS_API_URL | No | Custom API URL (default: https://api.enagrams.com) |

Tools

| Tool | Description | |------|-------------| | sync | Report what you're working on + get back what teammates' agents are doing, recent decisions, conflicts, and meeting context | | decide | Record a decision so every agent in the workspace knows about it | | search | Semantic search over past team decisions |

How It Works

sync is the key tool. Every time an agent needs context, it also reports what it's working on. One round-trip, both directions.

Agent calls sync({
  files: "src/auth.js, src/middleware.js",
  task: "refactoring auth to use sessions",
  branch: "feature/session-auth"
})

→ Returns: other agents, relevant decisions, conflicts, meeting context

decide records a decision with rationale so other agents understand the why, not just the what.

Agent calls decide({
  title: "Use express-session instead of JWT",
  rationale: "Server components need server-side sessions. JWT adds complexity.",
  files: "src/auth/middleware.js"
})

search finds past decisions by meaning, not exact text.

Agent calls search({ query: "how we handle authentication" })

License

MIT