MCP

Thoth ships an MCP server so AI coding agents can run impact analysis and verification themselves. The server runs over local stdio, is bound to the repository it was launched in, and exposes no arbitrary-shell tool — agents can only invoke the same trusted checks the CLI can.

Setup

thoth mcp setup            # prints exact config for each client
thoth mcp setup --write    # writes project-scoped JSON configs (safe merge)
thoth mcp status           # see what's configured

--write merges { "mcpServers": { "thoth": … } } into project files without touching other servers. Codex uses TOML, so instructions are printed instead of written.

Cursor

Project config .cursor/mcp.json (or global ~/.cursor/mcp.json):

{
  "mcpServers": {
    "thoth": { "command": "thoth", "args": ["-C", "/path/to/repo", "mcp"] }
  }
}

Claude Code

claude mcp add thoth --scope user -- thoth -C /path/to/repo mcp

Codex

codex mcp add thoth -- thoth -C /path/to/repo mcp

or append to ~/.codex/config.toml:

[mcp_servers.thoth]
command = "thoth"
args = ["-C", "/path/to/repo", "mcp"]

Tools

Tool	Purpose
thoth_scan_project	Package manager, frameworks, checks, graph stats
thoth_analyze_change	Changed files/symbols/exports of the current diff
thoth_analyze_impact	Blast radius, risk, relevant tests, unknowns
thoth_find_relevant_tests	Tests linked to the change
thoth_verify_change	Run trusted checks and return the report
thoth_get_report	Fetch a saved report

All outputs are compact, bounded JSON with schemaVersion: 1. Shared inputs: staged, base, explain (impact only).

Security notes

—base revisions and report ids are validated before reaching Git or the filesystem.
—Verification runs the repository's own discovered scripts — apply the same trust standard as running them yourself. Thoth is not a sandbox.
—The server performs no network I/O; stdio only.