Use io.github.* with an org name

[TheBestMoshe]

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

I'm not sure if I'm missing something, but when I authenticate with mcp-publisher login github it authenticates with my GitHub account. However, when attempting to publish, I get an error:

Publishing to https://registry.modelcontextprotocol.io...
Error: publish failed: server returned status 403: {"title":"Forbidden","status":403,"detail":"You do not have permission to publish this server. You have permission to publish: io.github.TheBestMoshe/*. Attempting to publish: io.github.<org name>/<repo name>"}

Is publishing under org namespaces not supported? Or is there a way for me to select the org as part of login?

[sivakumarpcitrix]

I am also observing similar issue. @TheBestMoshe Did you find a solution for the same?

sivakumarp@micpvdipd1200:~$ mcp-publisher publish server.json
Publishing to https://registry.modelcontextprotocol.io...
Error: publish failed: server returned status 403: {"title":"Forbidden","status":403,"detail":"You do not have permission to publish this server. You have permission to publish: io.github./*. Attempting to publish: io.github.citrix/netscaler-console-mcp-server. If you're trying to publish to a GitHub organization, you may need to make your organization membership public in your GitHub settings: https://docs.github.com/en/account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership"}

[TheBestMoshe]

Nope, I did not find a solution to this particular issue.

However, I had anyway preferred to use a domain, but had been blocked by another issue, which was fixed.

#494 (comment)

[haiiibin]

The behavior is documented in authentication.mdx under "Personal vs. organization namespaces": GitHub auth always grants your personal namespace, and an organization namespace (io.github.<orgname>/*) is granted only if you are an Owner of that org. Ordinary org membership is not enough; the registry checks your membership role.

So a 403 whose detail says "You have permission to publish: io.github." means one of two things:

1. You are not an Owner (admin) of the organization. An org Owner has to publish, or your role has to be upgraded.
2. You are an Owner, but you authenticated in a way that cannot prove it. This especially bites token logins in CI: a classic PAT needs the read:org scope, and a fine-grained PAT needs Organization permissions -> Members -> Read-only (bound to that one org). Without that, GitHub reports no org membership for the token, and you silently get the personal namespace only.

For CI publishing there is also a route with no tokens at all: mcp-publisher login github-oidc inside a GitHub Actions workflow grants the namespace of the account that owns the repository, so a workflow living in the org's repo publishes under io.github.<orgname>/*. I publish two servers on every tag this way (from a personal repo, so it grants my personal namespace); the setup is in the registry's github-actions guide.