Should I use Github MCP for getting context for internal supporting services/platform OR Build a dedicated MCP for them #1230

Pre-submission Checklist

• I have checked that this question would not be more appropriate as an issue in a specific repository
• I have searched existing discussions and documentation for answers

Question Category

• Protocol Specification
• SDK Usage
• Server Implementation
• General Implementation
• Documentation
• Other

Your Question

In our organization, we have several supporting microservices consumed by user-facing microservices. We maintain internal libraries and OpenAPI specifications detailing how these microservices should be consumed.

I would like to make these resources accessible in Cursor via MCP. Additionally, I'd like to include organization-specific guidelines regarding infrastructure, architecture, code style, and recommended patterns or libraries.

However, I'm unsure whether it's preferable to:

• Build and maintain our own MCP server to expose these resources and documentation, or
• Utilize GitHub's MCP.

Could anyone share insights or recommendations based on their experience with similar scenarios?

Thanks in advance for your advice!