
Dungbeetle
dev.dungbeetlePublished by dungbeetle.devv0.1.0Updated Oct 24, 2026
Visual regression & snapshot testing for AI agents — list runs, read semantic diffs, review.
Overview
Dungbeetle is a local MCP server for visual regression and snapshot testing that lets an assistant list test runs, read semantic diffs and review results.
- What you can do
- List visual regression and snapshot test runs for AI agents and inspect their outcomes. Read semantic diffs to see what changed between snapshots. Review results so an assistant can help triage visual changes. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Useful when a project runs visual regression or snapshot tests and you want an assistant to help review runs and interpret diffs without leaving the chat. Best suited to teams already using Dungbeetle for visual testing.
- Requirements
- Runs as a local process over stdio, installed from the npm package dungbeetle-mcp, so Node.js is needed. Authentication is required through DUNGBEETLE_AGENT_TOKEN, minted with the dungbeetle login command, or alternatively DUNGBEETLE_CLIENT_ID with DUNGBEETLE_CLIENT_SECRET. DUNGBEETLE_SERVER_URL is only needed when self-hosting. Desktop only; network access to the Dungbeetle service.
Installation
In SourceWeft
- Open Dungbeetle in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.