open-digger

The OpenDigger MCP Server provides a set of tools and prompts to analyze GitHub repositories and extract insights across metrics, trends, and ecosystem data. Once the server is running, you can access six available tools that perform single-repo metrics retrieval, batch metric operations, multi-repo comparisons, trend analyses, ecosystem insights, and health diagnostics. Use these tools to quickly fetch repository metrics, compare repositories, and generate health or trend reports that you can feed into prompts for deeper analysis. The server also exposes three prompts focused on repository health, repository comparison, and developer activity insights to guide your explorations. To verify the server is working, you can issue a tools list RPC call through your MCP client and confirm that all six tools are reported as available, and that the server shows a healthy status in your client UI.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your machine
• Git available to clone the repository

Step-by-step installation:

1. Install dependencies

• git clone https://github.com/X-lab2017/open-digger-mcp-server.git
• cd open-digger-mcp-server
• npm install

2. Build the server (TypeScript)

• npm run build

3. Start the MCP server

• npm start

4. Optional: Configure Cursor MCP.json

• Create or update .cursor/mcp.json to point to the compiled index.js, for example: { "mcpServers": { "open-digger": { "command": "node", "args": ["/full/path/to/dist/index.js"], "cwd": "/full/path/to/project", "env": { "CACHE_TTL_SECONDS": "300" } } } }

5. Verify operation

• Ensure the server starts and outputs the expected confirmation, then connect via your MCP client (Cursor, MCP Inspector, or other compatible tools).

Environment variables and configuration tips:

• CACHE_TTL_SECONDS controls caching for metric results; adjust based on load and freshness needs (default 300).
• SSE_PORT and SSE_HOST can enable an optional Server-Sent Events interface if your deployment uses it.
• Ensure the absolute paths used in Cursor configuration (.cursor/mcp.json) reflect your runtime environment, especially if running inside containers or CI.

Common issues and tips:

• If the MCP server does not appear in Cursor, re-check the absolute path in .cursor/mcp.json and restart Cursor.
• For permission errors on dist/index.js, ensure the file is executable: chmod +x dist/index.js.
• If you rebuild or relocate the project, update the Cursor config with the new path to dist/index.js.
• When using Docker or other environments, ensure the working directory (cwd) matches the server’s runtime context and that environment variables are correctly forwarded.