Skip to content

Add server.json for MCP Server Registry publishing#211

Open
badmonster0 wants to merge 1 commit into
cocoindex-io:mainfrom
badmonster0:add-mcp-registry-server-json
Open

Add server.json for MCP Server Registry publishing#211
badmonster0 wants to merge 1 commit into
cocoindex-io:mainfrom
badmonster0:add-mcp-registry-server-json

Conversation

@badmonster0

Copy link
Copy Markdown
Member

Adds a server.json so cocoindex-code can be published to the official MCP Server Registry. Registering there auto-propagates the listing to downstream directories that crawl the registry (Glama, PulseMCP, best-of-mcp-servers), so it's the highest-leverage single listing.

Manifest uses the 2025-12-11 schema, name io.github.cocoindex-io/cocoindex-code, PyPI package cocoindex-code v0.2.37, uvx runtime, stdio transport, with mcp as the package argument.

⚠️ Verify before publishing: the package exposes two console scripts (ccc and cocoindex-code) and the MCP entry point is ccc mcp. With runtimeHint: uvx the registry will invoke uvx cocoindex-code mcp. Confirm that command actually launches the MCP server (i.e. the cocoindex-code entry point routes to the same CLI app). If not, adjust identifier/packageArguments accordingly (e.g. the package may need the default script to start the server, or use a different invocation).

To publish after merge: mcp-publisher login github (as a cocoindex-io org member) then mcp-publisher publish.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: LJ 🥥🌴 <linghua@cocoindex.io>
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