Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/guides/publishing/publish-server.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,7 @@ Add an `mcpName` field to your `package.json`:
### How It Works
- Registry fetches `https://registry.npmjs.org/your-npm-package`
- Checks that `mcpName` field matches your server name
- Update the version to be the version of your published npm package
Copy link
Member

Choose a reason for hiding this comment

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

This should probably live in instructions, or maybe in the 'example server.json' section - not the description of how the validation mechanism works

Copy link
Author

Choose a reason for hiding this comment

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

I did not find the "instructions" -- this is what was in front of me while I was using the software.
Updated to align with validation mechanism, since it is part of the validation which was why my server was not being published and I got an error.

- Fails if field is missing or doesn't match

### Example server.json
Expand Down Expand Up @@ -453,4 +454,4 @@ See these real-world examples of published servers:

## What You've Accomplished

You've successfully published your first MCP server to the registry! Your server is now discoverable by MCP clients and can be installed by users worldwide.
You've successfully published your first MCP server to the registry! Your server is now discoverable by MCP clients and can be installed by users worldwide.
Loading