MCP Server List

Submit to Raycast MCP Registry

The Model Context Protocol Registry extension in Raycast’s extension store, where official MCP servers are listed by a data-only pull request.

Open a reviewed data-only registry entry PR against Raycast’s extensions repository. Eligibility is checked before purchase.

Reviewed three-file data-only registry PRSources checked

What to prepare

  • You are the maker of the server: it is added to the official entries.
  • A remote Streamable HTTP https endpoint with OAuth or no authentication, or an npm package that needs no environment variables.
  • A plain-text name and a description of at most 300 characters; an icon URL and website are recommended.
  • No existing entry, and no open Raycast pull request, for the repository, endpoint, package or name.

A data entry, reviewed by people

The service adds one object, one changelog section and one README row. It never touches extension code, and it stops if Raycast’s contribution rules or the entry type change. Raycast decides inclusion and timing.

Submission workflow

  1. Run the free preflight: it checks ownership, the pinned Raycast rules and scans main and open pull requests for duplicates.
  2. Review the exact diff: the registry entry, the changelog section and the README table row.
  3. Authorize it; the service account opens one pull request from its fork with maintainer edits enabled.
  4. Track Raycast’s manual review; the entry is confirmed only once it is merged on main.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • A duplicate entry or an open pull request for the same server.
  • A server that is not officially yours, needs an API key header or environment variables, or fails Raycast’s review.

Primary sources

Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.

← Compare all destinations