Publishing any MCP server without GitHub OAuth

[federicovallucci]

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

Hi everyone :)
I am fairly new to the MCP registry and very happy to discover this project. I have read the documentation and tried to understand the project scope and goals.

I saw that to publish a server it is required a GitHub token. I was wondering if this project aims to support also scenarios where codebases are not in GitHub or scenarios where the registry has no access to GitHub. In my case, I was trying to deploy 3 MCP servers and publish them into a registry in a completely private network. Would it be possible to use another way of authenticate the publish step?

Thank you!

[haiiibin]

Answering an old thread since this still comes up, and the docs cover it well now:

GitHub is only one of the authentication options, and auth is only used to prove namespace ownership. The registry never reads your code, so the codebase does not need to live on GitHub at all.

For the official registry there is domain-based authentication: you publish under the reverse-DNS namespace of a domain you control (com.example/*) and prove ownership with either a DNS TXT record (mcp-publisher login dns) or an HTTP challenge (mcp-publisher login http). The exact key-generation commands are in authentication.mdx. One gotcha worth knowing: the TXT record must sit on the apex of the domain (SPF-style), not under a selector like _mcp-auth.example.com, and stale records from rotated keys must be removed or verification fails.

For the completely-private-network case: the registry is open source and self-hostable, so you can run your own instance inside the network and point clients at it. Publishing to your own instance is then governed by whatever auth you configure there; GitHub is not involved at any step.

[nomanrafiqkhan262524-a11y]

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

Hi everyone :) I am fairly new to the MCP registry and very happy to discover this project. I have read the documentation and tried to understand the project scope and goals.

I saw that to publish a server it is required a GitHub token. I was wondering if this project aims to support also scenarios where codebases are not in GitHub or scenarios where the registry has no access to GitHub. In my case, I was trying to deploy 3 MCP servers and publish them into a registry in a completely private network. Would it be possible to use another way of authenticate the publish step?

Thank you!