Skip to content

docs(quickstart): document remote-only publishing - #1674

Merged
rdimitrov merged 1 commit into
modelcontextprotocol:mainfrom
baochipham942-eng:docs/1656-remote-only-quickstart
Oct 6, 2026
Merged

rdimitrov merged 1 commit into
modelcontextprotocol:mainfrom
baochipham942-eng:docs/1656-remote-only-quickstart

Conversation

@baochipham942-eng

Copy link
Copy Markdown
Contributor

Summary

Document the remote-only publishing path in the quickstart so authors do not have to infer how a server with no package is represented.

  • explain that packages can be omitted when remotes is present
  • add a minimal server.json example for a public Streamable HTTP endpoint
  • clarify GitHub namespace verification versus ownership of the remote URL's domain
  • surface the 100-character description limit
  • mark the npm account prerequisite as package-only

Validation

  • GOCACHE=/private/tmp/mcp-registry-go-cache GOMODCACHE=/private/tmp/mcp-registry-go-modcache go run tools/validate-examples/main.go
  • git diff --check

Fixes #1656

@rdimitrov
rdimitrov merged commit 69fc895 into modelcontextprotocol:main Oct 6, 2026
4 checks passed
rdimitrov added a commit that referenced this pull request Oct 6, 2026
## Summary

Follow-up to #1674, covering the remaining gaps from #1656.

- **`remote-servers.mdx`**: new "Ownership Verification" section. The
Registry verifies control of the namespace in `name`, but no
authentication method (GitHub, DNS, HTTP) verifies control of the remote
URL. Suggests DNS/HTTP authentication when the URL is on a domain you
control. Also documents that each remote URL can belong to only one
server name (`validateNoDuplicateRemoteURLs`).
- **Quickstart**: notes that `mcp-publisher init` always generates a
`packages` entry (it defaults to npm), which remote-only servers must
replace with `remotes`.
- **Quickstart**: remote-only publishers can skip the Node.js
prerequisite as well as npm.
- **Quickstart**: removes the duplicate 100-character `description`
note. The Step 4 note remains, and remote-only readers pass through Step
4.

## Validation

- `go run tools/validate-examples/main.go`
- `git diff --check`

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

Docs: remote-only server publishing has no documented path (verification, optional packages, description limit)

2 participants