Skip to content

Add server.json for MCP Registry publishing - #1432

Open
jy7lsna wants to merge 1 commit into
caura-ai:mainfrom
jy7lsna:add-mcp-registry-server-json
Open

jy7lsna wants to merge 1 commit into
caura-ai:mainfrom
jy7lsna:add-mcp-registry-server-json

Conversation

@jy7lsna

@jy7lsna jy7lsna commented Sep 9, 2026

Copy link
Copy Markdown

Adds a top-level server.json so Caura can be published to the official MCP Registry.

The registry does not accept PRs for listings — publishing is done with the mcp-publisher CLI, which reads this file. This PR is the prerequisite; the actual publish is one command after merge.

What's declared

  • Name: io.github.caura-ai/caura
  • Remote: https://caura.ai/mcp (streamable-http), with X-API-Key marked required + secret
  • Version: 3.4.1 (matches backend-v3.4.1)

Remote-only, so no package ownership verification is needed — nothing has to change in the npm/PyPI/Docker publish workflows.

Validated against server.schema.json (2025-12-11) from modelcontextprotocol/registry.

To publish after merge

mcp-publisher login github   # as a caura-ai org member, for the io.github.caura-ai/ namespace
mcp-publisher publish

🤖 Generated with Claude Code

https://claude.ai/code/session_01VVvqznDdoMdjtS7jPaZ3Mv

Declares the hosted Caura MCP endpoint (https://caura.ai/mcp,
streamable-http) so the server can be published to the official MCP
Registry with `mcp-publisher publish`.

Remote-only, so no package ownership verification is needed. Publishing
requires `mcp-publisher login github` as a caura-ai member, since the
namespace is io.github.caura-ai/caura.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VVvqznDdoMdjtS7jPaZ3Mv
@jy7lsna
jy7lsna requested a review from a team as a code owner September 9, 2026 12:28

This branch has not been deployed

No deployments
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