Skip to content

feat: publish the hosted server to the official MCP registry - #41

Merged
francescobianco merged 1 commit into
mainfrom
feat/mcp-registry
Oct 16, 2026
Merged

francescobianco merged 1 commit into
mainfrom
feat/mcp-registry

Conversation

@francescobianco

Copy link
Copy Markdown
Member

Lists the hosted Openapi® MCP server in the official MCP registry as io.github.openapi/mcp-server, so MCP clients and directories that read the registry (PulseMCP and others) can find it.

What's in it

  • server.json (schema 2025-12-11): a remote entry for https://mcp.openapi.com/ over streamable HTTP, with a required, secret Authorization: Bearer {token} header. Clients ask the user for the token, which is created at https://console.openapi.com/oauth.
  • .github/workflows/mcp-registry.yml: publishes with GitHub OIDC on every published release or by hand. It takes the version from pyproject.toml, so no token is stored in the repo.
  • glama.json to claim the Glama listing for the org repo.

Checked

  • mcp-publisher validate against the live registry: valid.
  • https://mcp.openapi.com/ answers initialize over streamable HTTP (serverInfo "OpenAPI.com MCP Gateway").

Next step, not in this PR: add the openapi-mcp-sdk PyPI package to server.json. The registry verifies it through an mcp-name: io.github.openapi/mcp-server line in the PyPI README (docs/readme-pypi.md), so it needs a new PyPI release.

🤖 Generated with Claude Code

- server.json lists https://mcp.openapi.com/ (streamable HTTP, Bearer
  token header) as io.github.openapi/mcp-server
- .github/workflows/mcp-registry.yml publishes it with GitHub OIDC on
  every release or by hand, keeping the version in sync with pyproject
- glama.json claims the Glama listing for the org repo

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@francescobianco
francescobianco merged commit 0fd4ca5 into main Oct 16, 2026
2 of 5 checks passed
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.

1 participant