Skip to content

Web UI for the official registry #99

Closed

Description

@tadasant

Primary purpose: sunset the modelcontextprotocol/servers README.

Activity

  1. added
    not go-live blockerThis issue has been reviewed and determined to not be a blocker to go-live
    on May 27, 2025
  2. LouisCan commented on Jul 11, 2025

    @LouisCan

    I developed a corresponding front-end page project based on ModelContextProtocol/Registry
    https://github.com/LouisCan/mcp-registry-frontend

    Image
  3. vemonet commented on Oct 10, 2025

    @vemonet
    Contributor

    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/

    • 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
  4. jonathanhefner commented on Oct 15, 2025

    @jonathanhefner
    Member

    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).

  5. changed the title [-]UI for the official registry[/-] [+]Web UI for the official registry[/+] on Nov 7, 2025
  6. domdomegg commented on Nov 7, 2025

    @domdomegg
    Member

    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:

    • 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
    • Status indicators (health, version info)

    Implementation: vanilla HTML/CSS/JS (~500 lines), calls existing /v0/servers, /v0/health, /v0/version endpoints.

    Technical approach

    Add a handler in internal/api/handlers/v0/ui.go that serves embedded HTML:

    //go:embed ui/index.html
    var embedUI string
    
    func HandleUI(ctx context.Context, input *struct{}) (*struct{ Body string }, error) {
        return &struct{ Body string }{Body: embedUI}, nil
    }

    Register route in internal/api/router/router.go replacing the current redirect.

    Create internal/api/ui/index.html with inline CSS and JS.

  7. added a commit that references this issue on Nov 7, 2025
    93d98ca
  8. added a commit that references this issue on Nov 10, 2025
    8cf317a
  9. added a commit that references this issue on Nov 20, 2025
    3e175be
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestnot go-live blockerThis issue has been reviewed and determined to not be a blocker to go-live

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions