Skip to content

chore(053): refresh registry server.json + publish guide (WP-D2)#509

Merged
Dumbris merged 1 commit into
mainfrom
chore/053-server-json-registry
May 22, 2026
Merged

chore(053): refresh registry server.json + publish guide (WP-D2)#509
Dumbris merged 1 commit into
mainfrom
chore/053-server-json-registry

Conversation

@Dumbris
Copy link
Copy Markdown
Member

@Dumbris Dumbris commented May 22, 2026

Summary

Updates the MCP registry server.json from stale v0.21.2 to the current v0.33.1 release, adds missing fields, and adds a publish guide.

Changes

server.json

  • Bump version from 0.21.2 to 0.33.1 (matches latest git tag)
  • Add title (MCPProxy) and websiteUrl (https://mcpproxy.app)
  • Populate remotes[] with a streamable-http entry at http://localhost:8080/mcp — the actual transport MCP clients use to connect to a running mcpproxy serve instance
  • packages[] remains empty: the supported registryType values (npm, pypi, oci, nuget, mcpb) have no match for Homebrew tap / GitHub release tarballs / go install. The Docker server-edition image (ghcr.io/smart-mcp-proxy/mcpproxy-server) is gated behind if: false in the release workflow and is not yet published.

docs/mcp-registry-publishing.md (new)

  • Install mcp-publisher via Homebrew
  • GitHub interactive and OIDC auth for the io.github.smart-mcp-proxy namespace
  • Validate (mcp-publisher validate + offline check-jsonschema) and publish commands
  • Deprecate/delete lifecycle commands
  • Notes on what requires human auth and how to automate via CI OIDC

Validation

server.json validated against the official schema:

uvx check-jsonschema --schemafile \
  https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json \
  server.json
# ok -- validation done

What still requires the user

Publishing to the registry requires authenticating as a member of the smart-mcp-proxy GitHub org (mcp-publisher login github). This PR prepares the artifact; the actual mcp-publisher publish command must be run manually or wired into the release workflow with id-token: write OIDC permission.

- Bump version from 0.21.2 to 0.33.1 (latest release tag)
- Add title, websiteUrl fields
- Populate remotes[] with streamable-http transport at localhost:8080/mcp
  (packages[] stays empty: Homebrew/GitHub-release/go-install channels have
   no matching registryType in the schema; Docker server image not yet published)
- Add docs/mcp-registry-publishing.md with mcp-publisher CLI steps,
  GitHub namespace auth, validate/publish commands, and CI automation notes
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying mcpproxy-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 06d5c06
Status: ✅  Deploy successful!
Preview URL: https://7a97e0d0.mcpproxy-docs.pages.dev
Branch Preview URL: https://chore-053-server-json-regist.mcpproxy-docs.pages.dev

View logs

@codecov-commenter
Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions
Copy link
Copy Markdown

📦 Build Artifacts

Workflow Run: View Run
Branch: chore/053-server-json-registry

Available Artifacts

  • archive-darwin-amd64 (27 MB)
  • archive-darwin-arm64 (25 MB)
  • archive-linux-amd64 (16 MB)
  • archive-linux-arm64 (14 MB)
  • archive-windows-amd64 (27 MB)
  • archive-windows-arm64 (24 MB)
  • frontend-dist-pr (0 MB)
  • installer-dmg-darwin-amd64 (20 MB)
  • installer-dmg-darwin-arm64 (18 MB)

How to Download

Option 1: GitHub Web UI (easiest)

  1. Go to the workflow run page linked above
  2. Scroll to the bottom "Artifacts" section
  3. Click on the artifact you want to download

Option 2: GitHub CLI

gh run download 26280353552 --repo smart-mcp-proxy/mcpproxy-go

Note: Artifacts expire in 14 days.

@Dumbris Dumbris merged commit 13dd523 into main May 22, 2026
28 checks passed
@Dumbris Dumbris deleted the chore/053-server-json-registry branch May 22, 2026 09:56
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