You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
directly hits the MCP registry API to enable doing basic search (using corsproxy.io for now, waiting for CORS to be enabled on the main registry)
extract and present in a user-friendly manner most informations available for each server (including packages and remote servers details, such as env var and headers)
"install in VSCode/Cursor" button for each package/remote of each server (one click install using the vscode:// or cursor:// protocols)
enable to build a "stack" (list) of MCP servers, that can then be exported all at once as VSCode mcp.json or Cursor config
This may have been discussed elsewhere, but I'm wondering if, instead of having a UI for the official registry, we could have an easily discoverable page that links to downstream marketplaces (possibly based off of community projects).
I think it would be good to get out a minimal website to have something there. Something very scrappy, not to get attached to long term but to have a starting point. My guess is we'd rewrite it later once we understand usage better, but having something live is better than nothing.
I imagine this as a single self-contained HTML file at / (replacing the current redirect). Zero dependencies, embedded in the Go binary using //go:embed.
Goals:
Publishers can verify their server appeared after publishing
Provide a simple web interface to browse the registry
Replace the modelcontextprotocol/servers README as the canonical list
Clearly disambiguate this from the GitHub MCP registry
I'll probably take a stab at this later today/this weekend.
Features
Server list with:
Search (by name)
Pagination
Expandable rows showing full metadata, versions, packages, repository links
Activity
LouisCan commentedon Jul 11, 2025
I developed a corresponding front-end page project based on ModelContextProtocol/Registry
https://github.com/LouisCan/mcp-registry-frontend
vemonet commentedon Oct 10, 2025
Hi, as I was frustrated with existing MCP registries browsers, and could not wait for the frontend to be out so I made a single page app for it using vite, react, and shadcn/ui: https://vemonet.github.io/mcp-registry/
vscode://orcursor://protocols)mcp.jsonor Cursor configjonathanhefner commentedon Oct 15, 2025
This may have been discussed elsewhere, but I'm wondering if, instead of having a UI for the official registry, we could have an easily discoverable page that links to downstream marketplaces (possibly based off of community projects).
Add hint icon to in-browser UI community projects (#679)
[-]UI for the official registry[/-][+]Web UI for the official registry[/+]domdomegg commentedon Nov 7, 2025
v0 plan
I think it would be good to get out a minimal website to have something there. Something very scrappy, not to get attached to long term but to have a starting point. My guess is we'd rewrite it later once we understand usage better, but having something live is better than nothing.
I imagine this as a single self-contained HTML file at
/(replacing the current redirect). Zero dependencies, embedded in the Go binary using//go:embed.Goals:
I'll probably take a stab at this later today/this weekend.
Features
Server list with:
Implementation: vanilla HTML/CSS/JS (~500 lines), calls existing
/v0/servers,/v0/health,/v0/versionendpoints.Technical approach
Add a handler in
internal/api/handlers/v0/ui.gothat serves embedded HTML:Register route in
internal/api/router/router.goreplacing the current redirect.Create
internal/api/ui/index.htmlwith inline CSS and JS.Add simple web UI for browsing the registry
Add simple web UI for browsing the registry (modelcontextprotocol#757)
Add simple web UI for browsing the registry (modelcontextprotocol#757)
Add hint icon to in-browser UI community projects (modelcontextprotoc…