ci(mcp): auto-publish server.json to the MCP registry (+ Smithery)#399
Merged
Conversation
Adds server.json (dev.stitchapi/docs — remote Streamable-HTTP server, tools search_docs + get_doc) at the repo root, plus a workflow that publishes it to the official MCP registry via domain auth and to Smithery (idempotent upsert). The registry publish cascades to Glama + PulseMCP automatically. Safety: PRs run mcp-publisher validate only; the publish jobs never run on a PR and stay green/inert until MCP_PRIVATE_KEY / SMITHERY_API_KEY are set, so merging does not trigger an accidental publish or a red run. Each registry publish needs a unique version; workflow_dispatch forces a publish. One-time domain setup is in docs/MCP-PUBLISHING.md. Verified against modelcontextprotocol/registry (v1.7.9). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
System openssl on macOS is LibreSSL, which fails Ed25519 keygen with 'Algorithm Ed25519 not found'. Lead with openssl@3 via an arch-independent `brew --prefix` path, and add an ECDSA P-384 no-install fallback. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The MCP registry keygen in docs/MCP-PUBLISHING.md writes key.pem; ignoring *.pem/*.key keeps a private key from being committed by accident. Keys live in GitHub Actions secrets, not the repo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Automates publishing the hosted docs MCP to the MCP registries.
server.json(repo root) — the registry manifest fordev.stitchapi/docs, a remote Streamable-HTTP server (toolssearch_docs+get_doc)..github/workflows/publish-mcp.yml— on aserver.jsonversion bump merged tomain(or a manual dispatch), publishes to the official MCP registry via domain auth, and to Smithery (idempotent upsert). The registry publish cascades to Glama + PulseMCP automatically, so those need no step.docs/MCP-PUBLISHING.md— the one-time setup (key generation, thestitchapi.devapex DNS-TXT record, the two secrets).Behavior & safety
server.jsonrunmcp-publisher validateonly — an invalid manifest is caught before merge; nothing is published. (This PR self-validates.)MCP_PRIVATE_KEYfor the registry,SMITHERY_API_KEYfor Smithery). So merging this won't produce a red run or an accidental publish.version(the registry rejects duplicates); the workflow guards on that, andworkflow_dispatchis the explicit "publish now" once your domain is verified.To go live (one-time, yours — you said you can do the domain verification)
stitchapi.dev—v=MCPv1; k=ed25519; p=…(apex, not a_mcpselector).MCP_PRIVATE_KEY(hex) as a repo secret.SMITHERY_API_KEY, confirm the-n owner/name.Exact commands are in
docs/MCP-PUBLISHING.md; the flow is verified againstmodelcontextprotocol/registry(mcp-publisher v1.7.9). Registry is officially in preview.Merge is yours — publishing only starts once you add the secret + DNS record.
🤖 Generated with Claude Code