Skip to content

Conversation

@Neilblaze
Copy link

Description

Adding OpenDigger MCP server to the community servers list in README.md.

Server Details

  • Server: OpenDigger MCP Server (new entry)
  • Changes to: Community servers documentation section

Motivation and Context

This adds the OpenDigger MCP server (https://github.com/X-lab2017/open-digger-mcp-server) to the community servers list, making it discoverable to users who wish to interact with OpenDigger's MCP server using natural language. The server allows querying advanced repository analytics and provides insights through various tools and prompts.

How Has This Been Tested?

  • ✅ Tested with Claude Desktop using MCP Inspector
  • ✅ Tested with Cursor, VSCode, and Windsurf
  • ✅ All tools validated and working

Breaking Changes

None — this is a documentation update only.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Note

Server supports all 21 OpenDigger metrics. For more, follow the features section in the docs.

@Neilblaze
Copy link
Author

cc'ing @birdflyi & @frank-zsy for greater visibility.

@olaservo
Copy link
Member

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2913

@olaservo olaservo closed this Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants