Add MCP registry metadata (server.json + mcpName) - #12
Merged
Conversation
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.
…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
There was a problem hiding this comment.
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.
- 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)
HungKNguyen
approved these changes
Aug 27, 2026
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.
Summary
server.jsonat the repo root and anmcpNamefield topackage.json, the two things required to publish this server to the official MCP registry (registry.modelcontextprotocol.io).io.github.PSPDFKit/nutrient-document-engine-mcp-server(GitHub-auth).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 publishPlease confirm at dry-run time:
server.jsonandpackage.jsonare both0.0.1, but npm latest is0.0.2. Reconcile these (bump repo to the version you'll publish) before publishing; the registry validates thatserver.jsonversion matches the published npm version.$schemadate is current (dry-run flags if stale).DOCUMENT_ENGINE_BASE_URL(required) andDOCUMENT_ENGINE_API_AUTH_TOKEN(required/secret).ACTIVATION_KEYis 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.jsonandserver.jsonboth parse as valid JSON.mcp-publisher publish --dry-runpasses (run by a maintainer).