Analyze GitHub Repositories with Advanced Metrics

OpenDigger MCP Server gives an AI assistant advanced repository analytics through OpenDigger, an open-source project health and community metrics platform. It provides 6 tools and 3 guided prompts for fetching metrics, comparing repositories, analyzing growth trends, and generating health reports.

Use it when you want to compare two repositories' activity (e.g. microsoft/vscode vs facebook/react), generate a comprehensive health report for a project, analyze contributor growth trends over a time period, or pull ecosystem-wide analytics. It covers core metrics (openrank, stars, forks, contributors, participants, issues_new/issues_closed, pull_requests, commits, activity), extended metrics (technical_fork, bus_factor, releases, inactive_contributors, maintainer_count, community_activity), and additional metrics (change_requests, pull_requests_accepted/merged, issue_comments, issue_response_time, code_change_lines, developer_network). Do not rely on server_health for production monitoring - it's explicitly marked Beta. Detailed installation instructions and configuration options for different IDEs are maintained separately in the project's own INSTALLATION.md file.

Tools: get_open_digger_metric (single repository metric), get_open_digger_metrics_batch (batch fetch multiple metrics), compare_repositories (multi-repository comparison), analyze_trends (growth trend analysis over time), get_ecosystem_insights (ecosystem-wide analytics), server_health (system diagnostics, Beta).

Prompts: repo_health_analysis (comprehensive repository health report), repo_comparison (competitive repository analysis), developer_insights (developer activity and contribution analysis).

Example queries: "Compare microsoft/vscode and facebook/react using the compare_repositories tool," "Generate a health report for microsoft/vscode using the repo_health_analysis prompt," "Analyze the growth trends for contributors in microsoft/vscode over 2 years."

# Setup
git clone https://github.com/X-lab2017/open-digger-mcp-server.git

cd open-digger-mcp-server && cd mcp-server
npm install
npm run build

# Start server
npm start

For Cursor, configure .cursor/mcp.json:

{
  "mcpServers": {
    "open-digger": {
      "command": "node",
      "args": ["/full/path/to/dist/index.js"],
      "cwd": "/full/path/to/project",
      "env": { "CACHE_TTL_SECONDS": "300" }
    }
  }
}

Also compatible with VS Code, Claude Chat, or the official MCP Inspector. Optional environment variables include CACHE_TTL_SECONDS (cache duration) and SSE_PORT/SSE_HOST for an optional SSE server. Verify the server works with echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | node dist/index.js, which should list all 6 tools.

Cursor users can confirm the server loaded correctly by checking for a green status dot next to "open-digger-mcp", "6 tools" and "3 prompts" displayed in the server status, and no error indicators. Common troubleshooting steps include verifying absolute paths in .cursor/mcp.json, restarting Cursor completely, running chmod +x dist/index.js for permission errors, and clearing the npm cache (npm cache clean --force) followed by a rebuild for stale-cache issues.

Open-source maintainers, engineering managers, and researchers who want AI-assisted analysis of repository health, contributor activity, and ecosystem trends instead of manually digging through GitHub stats.