Skip to content

Add MCP registry metadata (server.json + mcpName) - #12

Open
jdrhyne wants to merge 4 commits into
mainfrom
jdrhyne/mcp-registry-metadata
Open

Add MCP registry metadata (server.json + mcpName)#12
jdrhyne wants to merge 4 commits into
mainfrom
jdrhyne/mcp-registry-metadata

Conversation

@jdrhyne

@jdrhyne jdrhyne commented Jul 24, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds server.json at the repo root and an mcpName field to package.json, the two things required to publish this server to the official MCP registry (registry.modelcontextprotocol.io).
  • Namespace: io.github.PSPDFKit/nutrient-document-engine-mcp-server (GitHub-auth).
  • No runtime code changed. Metadata only.

Why

Publishing once to the official registry cascades automatically to Glama, PulseMCP, and mcp.so. Today this server has no server.json, so it isn't in the official registry.

Before publishing (maintainer checklist)

brew install mcp-publisher
mcp-publisher login github        # needs push access to PSPDFKit
mcp-publisher publish --dry-run
mcp-publisher publish

Please confirm at dry-run time:

  • Version alignmentserver.json and package.json are both 0.0.1, but npm latest is 0.0.2. Reconcile these (bump repo to the version you'll publish) before publishing; the registry validates that server.json version matches the published npm version.
  • $schema date is current (dry-run flags if stale).
  • env vars complete — I included DOCUMENT_ENGINE_BASE_URL (required) and DOCUMENT_ENGINE_API_AUTH_TOKEN (required/secret). ACTIVATION_KEY is a Document Engine deployment setting, not an MCP client env, so it's intentionally excluded — add it if the server itself reads it.

Test plan

  • package.json and server.json both parse as valid JSON.
  • Diff is metadata-only (package.json +1 line, new server.json).
  • mcp-publisher publish --dry-run passes (run by a maintainer).

Adds server.json at repo root and an mcpName field to package.json so this
server can be published to the official MCP registry (registry.modelcontextprotocol.io),
which cascades to Glama, PulseMCP, and mcp.so. Namespace io.github.PSPDFKit/*.
No runtime code changed.
@jdrhyne jdrhyne self-assigned this Jul 24, 2026
…n server.json

npm latest is 0.0.2 (published without a corresponding git commit); the registry validator requires mcpName inside the published package, so the next publish is 0.0.3. server.json now marks the auth token secret/required and lists the optional dashboard, log-level and transport variables.

Claude-Session: https://claude.ai/code/session_0168QbHA5yAyXyYLUfPxvSoQ

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds metadata required to publish the server to the official MCP registry.

Changes:

  • Adds the MCP registry manifest.
  • Aligns package and registry versions at 0.0.3.
  • Adds npm ownership verification metadata.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
server.json Defines registry identity, package, transport, and environment metadata.
package.json Updates the version and adds mcpName.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread server.json Outdated
Comment thread server.json Outdated
- Shorten server.json description to the registry's 100-character limit
- Drop MCP_TRANSPORT from the stdio package metadata (an installing client must not be able to launch HTTP mode through the stdio entry)
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.

2 participants