MCP Registry Server MCP server

Endpoint: https://registry.run.mcp.com.ai/mcp · Authentication: No auth

MCP interface for searching and publishing servers through the official Model Context Protocol Registry backend.

Test it live Run the release-readiness report

How do I authenticate?

Add the endpoint directly in your client. The catalog records no authentication requirement; no OAuth sign-in or API key is configured in this setup. The live server may change.

Authentication and connection guide

Connection specification

Remote endpoint: https://registry.run.mcp.com.ai/mcp
Browser access: Direct browser connection verified
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Streamable HTTP — Observed by the latest catalog validation
Declared authentication: No authentication
Detected authentication: No authentication detected or retained from publisher evidence
Protocol lifecycle: Stateful MCP · 2025-06-18
Category: Developer Tools

Product documentation · Source repository · Official listing documentation · Official MCP Registry record

More Developer Tools MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

No app registration needed

This catalog entry does not require authorization or provider app registration.

Connect it

Browser-verified endpoint: https://registry.run.mcp.com.ai/mcp · Streamable HTTP. No authentication is required by the catalog listing.

Agent prompt for Claude Code or Codex

Add the MCP Registry Server MCP server to my MCP client configuration and verify that it works.

What it is: MCP interface for searching and publishing servers through the official Model Context Protocol Registry backend.
Server URL: https://registry.run.mcp.com.ai/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: none. The server accepts connections without credentials.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/mcp-registry/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "mcp-registry" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user 'mcp-registry' 'https://registry.run.mcp.com.ai/mcp'
   Codex: codex mcp add 'mcp-registry' --url 'https://registry.run.mcp.com.ai/mcp'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user 'mcp-registry' 'https://registry.run.mcp.com.ai/mcp'

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'mcp-registry' --url 'https://registry.run.mcp.com.ai/mcp'

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "mcp-registry": {
      "url": "https://registry.run.mcp.com.ai/mcp"
    }
  }
}

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "mcp-registry": {
      "type": "http",
      "url": "https://registry.run.mcp.com.ai/mcp"
    }
  }
}

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Client compatibility

Client	Status	Why
Claude Code	Supported	Claude Code supports Streamable HTTP servers and servers without authentication.
Codex	Partial	Codex's documentation does not state support for servers without authentication.
Cursor	Supported	Cursor supports Streamable HTTP servers and servers without authentication.
VS Code	Supported	VS Code supports Streamable HTTP servers and servers without authentication.
Claude	Supported	Claude supports Streamable HTTP servers and servers without authentication.
Claude Desktop	Supported	Claude Desktop supports Streamable HTTP servers and servers without authentication.
ChatGPT	Partial	Stateful routing needs operational care: ChatGPT can preserve MCP sessions, but the deployment must route a session consistently and retain its state.
Windsurf	Partial	Windsurf's documentation does not state support for servers without authentication.
Gemini CLI	Supported	Gemini CLI supports Streamable HTTP servers and servers without authentication.
MCP SDK	Supported	MCP SDK supports Streamable HTTP servers and servers without authentication.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

GitHub — GitHub's official hosted MCP server for repository context, issues, pull requests, code search, and development workflows. OAuth 2.1
GitLab — GitLab's hosted MCP server exposes project, issue, merge-request, pipeline, and repository workflows. OAuth 2.1
CircleCI — CircleCI's hosted MCP server helps inspect pipelines, builds, tests, failures, and delivery workflows. OAuth 2.1
Sanity — Runs GROQ queries, creates and patches documents, manages releases, and reads schemas in Sanity projects. Uses OAuth by default; Sanity also documents token-based authentication. OAuth 2.1
Buildkite — Reads Buildkite pipelines, builds, jobs, logs, artifacts, and test results. This endpoint uses OAuth; headless agents can send an API token to the /direct endpoint. OAuth 2.1
Jam — Reads Jam bug reports, including console logs, network requests, user events, and screenshots, so assistants can debug captured issues. Requires Jam OAuth. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain MCP Registry Server? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/mcp-registry.svg)](https://mcptest.io/servers/mcp-registry/)

HTML

<a href="https://mcptest.io/servers/mcp-registry/"><img src="https://mcptest.io/badge/server/mcp-registry.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/mcp-registry.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/mcp-registry/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 2:08 PM
Validation detail: Negotiated stateful MCP 2025-06-18 at https://registry.run.mcp.com.ai/mcp; detected transport streamable-http; authentication none

Tool inventory

Inventory not observed

The catalog validator has not recorded a complete public tool listing for MCP Registry Server. Connect in the Playground to list its tools live.