MCP server

The Dungbeetle MCP server — dungbeetle-mcp — lets coding agents such as Claude Code, Cursor, Codex, and Gemini CLI triage snapshot runs and approve baselines directly, without leaving their tool loop.

It is self-hostable and runs against your own Dungbeetle server, so nothing is sent to a third-party cloud. The design follows one principle: agents get low-token structured diff summaries (what changed, where, how severe), never base64 screenshots — images stay behind a review URL a human opens.

Deterministic diffs, human-owned approval. The agent reads and triages; mutating a baseline is a destructiveHint tool, so your MCP client asks for human confirmation before it runs.

What it talks to

dungbeetle-mcp is a thin client over the server's /api/v1 surface. It authenticates with an agent token — a scoped, revocable credential a human mints with dungbeetle login and can revoke at /ui/agents — or, CI-style, with a repository's client_id / client_secret pair. Either way, everything it can see or change is scoped to one repository; with an agent token, scopes further limit which tools work and every review is attributed to the agent acting on the human's behalf. The agent discovers work itself: dungbeetle_list_runs finds recent runs, so "triage my latest failure" needs no run id pasted in.

Capture stays in the CLI (dungbeetle ci → dungbeetle push); the MCP server is the review and approval surface over the runs you've pushed.

Next: set it up — or jump straight to Claude Code, Cursor, Codex, or Gemini CLI — then read agent authentication and the tools and agent loop.