Skip to content

docs: explain publishing community servers to the MCP Registry - #4726

Closed
CryoThrust wants to merge 1 commit into
modelcontextprotocol:mainfrom
CryoThrust:docs/community-registry-publishing
Closed

CryoThrust wants to merge 1 commit into
modelcontextprotocol:mainfrom
CryoThrust:docs/community-registry-publishing

Conversation

@CryoThrust

Copy link
Copy Markdown
Contributor

Summary

Addresses #4171 by documenting the recommended path for community-built MCP servers:

  • Directs community projects to the MCP Registry instead of this reference-server repository.
  • Lists the artifact, server.json, validation, authentication, and publication steps.
  • Documents the GitHub namespace requirement and links to the Registry's current quickstart.
  • Clarifies that reference-server issues should continue to be reported here.

Verification

  • git diff --check
  • README assertions for the Registry commands and namespace

olaservo added a commit that referenced this pull request Sep 2, 2026
…eled (#4739)

Observed on #4714 and #4726: addLabels returned 403 "Resource not
accessible by integration" because pull_request gives fork PRs a
read-only token. The job only calls the GitHub API and never checks
out PR code, so pull_request_target is safe here.


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

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@cliffhall cliffhall added the closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875) label Oct 20, 2026
@cliffhall

Copy link
Copy Markdown
Member

Thank you for this pull request, and apologies for the long wait for a response.

These servers are reference implementations: they exist to show how each part of MCP is used, not to be general-purpose products, so new features are taken selectively, and this change isn't one the maintainers plan to take. This repository also now accepts issues, not pull requests, from anyone but its maintainers; the policy is in CONTRIBUTING.md.

This is not a judgment on the idea or on you. A server in the MCP Registry may well offer it, and anyone is welcome to build on these servers to do so. If you think we've misread it, please open an issue describing the problem and the expected behavior.

This is part of the backlog triage in #4875.

@cliffhall cliffhall closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closed-out-of-scope Closed: out of scope here; listings and new servers go to the MCP Registry (#4875)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants