Skip to content

Set up the MCP server

The server is bundled with dungbeetle-server. Provide the repository credentials in the environment and launch over stdio:

sh
DUNGBEETLE_SERVER_URL=https://dungbeetle.example.com \
DUNGBEETLE_CLIENT_ID=cid_… \
DUNGBEETLE_CLIENT_SECRET=csec_… \
dungbeetle-mcp

stdout is the JSON-RPC channel; diagnostics go to stderr. Missing credentials exit non-zero with guidance.

Configure an MCP client

Most clients take a command + env. For example, a mcp.json / client config:

json
{
  "mcpServers": {
    "dungbeetle": {
      "command": "dungbeetle-mcp",
      "env": {
        "DUNGBEETLE_SERVER_URL": "https://dungbeetle.example.com",
        "DUNGBEETLE_CLIENT_ID": "cid_…",
        "DUNGBEETLE_CLIENT_SECRET": "csec_…"
      }
    }
  }
}

In Claude Code: claude mcp add dungbeetle --env DUNGBEETLE_SERVER_URL=… --env DUNGBEETLE_CLIENT_ID=… --env DUNGBEETLE_CLIENT_SECRET=… -- dungbeetle-mcp.

Source-available: CLI under FSL-1.1-ALv2, cloud server under BUSL-1.1. See Licensing.