MCP.so
Sign In

OpenDigger MCP Server

@X-lab2017

Basic information

Category

Other

License

Apache-2.0

Transports

stdio

Author

X-lab2017

About OpenDigger MCP Server

MCP server of OpenDigger

OpenDigger MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

OpenDigger MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is OpenDigger MCP Server?

An MCP server for OpenDigger that enables advanced repository analytics and insights through tools and prompts.

How to use OpenDigger MCP Server?

Clone the repository, run npm install and npm run build, then start with npm start. Configure the Cursor MCP client with the absolute path in .cursor/mcp.json. Verify by checking the 6 tools and 3 prompts appear.

Key features of OpenDigger MCP Server

  • 6 tools: get single metric, batch metrics, compare repositories, analyze trends, ecosystem insights, server health
  • 3 prompts: repo health analysis, repo comparison, developer insights
  • Metrics include core (openrank, stars, forks), extended (bus factor, releases), and additional (change requests, issue comments)
  • Configurable cache TTL (default 300 seconds) and optional SSE server on port 3001
  • Works with Cursor AI IDE and other MCP clients like VS Code, Claude Chat, MCP Inspector

Use cases of OpenDigger MCP Server

  • Compare repositories like microsoft/vscode and facebook/react using the compare_repositories tool
  • Generate comprehensive health reports for a specific repository using the repo_health_analysis prompt
  • Analyze growth trends for contributors over a period (e.g., 2 years) using analyze_trends
  • Perform batch metric retrieval and ecosystem insights for decision-making

Frequently asked questions

1

What runtime does OpenDigger MCP Server require?

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

2

How do I verify OpenDigger MCP Server is running?

After starting, check for the "OpenDigger MCP Server running (on stdio)" output. In Cursor, a green dot with "6 tools" and "3 prompts" should appear. Alternatively, use `echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | node dist/index.js` to list all tools.

3

What metrics can I access?

Core: openrank, stars, forks, contributors, participants, issues_new, issues_closed, pull_requests, commits, activity. Extended: technical_fork, bus_factor, releases, inactive_contributors, maintainer_count, community_activity. Additional: change_requests, pull_requests_accepted, pull_requests_merged, issue_comments, issue_response_time, code_change_lines, developer_network.

4

How do I configure environment variables?

Set `CACHE_TTL_SECONDS` (optional, default 300s) and `SSE_PORT`/`SSE_HOST` for optional SSE server in a `.env` file or in the MCP client's environment config.

5

What if the server doesn't appear in Cursor?

Verify absolute paths in `.cursor/mcp.json`, restart Cursor completely, and check MCP Settings for error messages. Run `chmod +x dist/index.js` if permission errors occur, or rebuild with `npm run clean && npm install && npm run build`.

Comments

More Other MCP servers