Question 1

What runtime does OpenDigger MCP Server require?

Accepted Answer

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

Question 2

How do I verify OpenDigger MCP Server is running?

Accepted Answer

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.

Question 3

What metrics can I access?

Accepted Answer

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.

Question 4

What credentials does it need?

Accepted Answer

It reads `CACHE_TTL_SECONDS` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

OpenDigger MCP Server

What is the OpenDigger MCP Server?

What it actually does

More MCP options

How to install the OpenDigger MCP Server

Configuration

Example prompts to try

Frequently asked questions

Alternatives to the OpenDigger MCP Server

Filesystem

Context7

Vibelogin-mcp

CleanCode AI

Agent-claim-mcp

Shyn