MCP

Connect coding agents to local eve product history.

eve exposes local product history to agents through the Model Context Protocol. This lets an agent read snapshots, complete a new snapshot, or check out a recorded implementation state through structured tools.

Transports

Stdio:

eve mcp-stdio

Streamable HTTP, after starting the local runtime:

eve

Connect the client to:

http://localhost:4317/mcp

Resources

eve://repos
eve://repos/{repoId}
eve://repos/{repoId}/snapshots
eve://repos/{repoId}/snapshots/{snapshotId}

Tools

  • list_repos
  • list_snapshots
  • get_snapshot
  • declare_plan
  • get_plan_request
  • pending_snapshot
  • complete_snapshot
  • skip_snapshot
  • checkout_snapshot

declare_plan persists a durable local Plan request and waits for approval when the connection survives. Agents should reuse the same planRequestId after timeout, cancellation, or restart. get_plan_request reads the current request state without waiting.

Approve and reject operations are intentionally exposed through the trusted localhost API and local UI, not through MCP.

skip_snapshot requires a non-empty reason and writes a durable .eve/skips/ record. Skips resolve reviewed committed ranges without appearing in Snapshot timelines, changelogs, counts, or search.

npx @nhestrompia/eve@latest install

This installs the platform-specific EVE binary and configures Codex, Claude Code, and opencode with its absolute path. To reconfigure MCP after EVE is installed:

eve install-mcp

Security model

Version 0 assumes trusted local usage. Keep local HTTP bound to localhost and only connect agent clients you trust.

On this page