Skip to main content

What is MCP?

The Model Context Protocol is an open standard that lets AI agents call structured tools. Enagrams ships an MCP server bundled with the enagrams npm package. Every tool below is callable from any MCP-compatible client (Cursor, Claude Code, Codex, Windsurf, custom).

Install

npx enagrams init writes the MCP config for every supported IDE automatically. If you’re setting up by hand:
The server speaks stdio to your IDE and HTTP to the Enagrams API.

Tools by Category

Coordination and Context

Core tools every agent calls several times a session.

Contracts

Interface contracts let one agent publish a shape — API response, type definition, function signature — and other agents query it. Contract changes surface in everyone’s next sync. Use ask (free-form) or search to discover existing contracts.

Workstreams

Workstreams map 1:1 to shared git branches ena/<slug> and enable symbol-level coordination with other participants.

The Test Gate

Gate changes before they land on a workstream. Two-phase: first call returns affected tests, second call submits results.

Negotiation

When two agents want the same symbol, negotiate_* runs a bounded-turn state machine with auto-resolution.

Tasks

Delegate follow-up work inside a workstream with dependency-based auto-unblocking.

Conventions and Decision Staleness

Living conventions layer on top of decisions. must-tier conventions are hard gates on PreToolUse. Stale decisions get surfaced for review when their linked code drifts.

How Agents Use Them

A typical session looks like:
Most tools accept an optional session_id; the MCP server also automatically scopes each call to your workspace.