OpenDigger MCP Server

MCP server of OpenDigger

Local serverstdioTypeScript

What is the OpenDigger MCP server?

MCP server of OpenDigger. The opendigger mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server for OpenDigger enabling advanced repository analytics and insights through tools and prompts.

Adding it to your client

The server ships on npm as npm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • No. — Tool
  • Metrics — The Metrics tool exposed by this server

Configuration

You will need one environment variable: CACHE_TTL_SECONDS. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the opendigger mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. OpenDigger's toolset — No., Metrics — is a fair guide to whether it matches your workflow. It is maintained by X-lab2017; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against OpenDigger's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
No.Tool
MetricsThe Metrics tool exposed by this server.

How to install the OpenDigger MCP server

### Cursor MCP (.cursor/mcp.json)
```json
{
  "mcpServers": {
    "open-digger": {
      "command": "node",
      "args": ["/full/path/to/dist/index.js"],
      "cwd": "/full/path/to/project",
      "env": {
        "CACHE_TTL_SECONDS": "300"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CACHE_TTL_SECONDSConfiguration value read at startup.Optional

Example prompts to try

  • Use OpenDigger to No..
  • Use OpenDigger to Metrics.

Frequently asked questions

Node.js; setup involves cloning, `npm install`, `npm run build`, then `npm start`.