MCP Registry Allowlist

Enterprise workspace admins can enforce an MCP registry so that only approved MCP servers are available to workspace members. Settings pages for personal, workspace, and project MCP servers hide servers the registry does not list. The registry protocol and schema are defined at registry.modelcontextprotocol.io.

Where the Registry Is Checked

The machine that starts an MCP server checks it against the registry:

  • Remote MCP servers added in settings, including servers that sign in with OAuth, are checked by ampcode.com.
  • Local MCP servers set up in the Amp CLI are checked by the CLI, or the runner, that starts them. In orb threads, the orb checks them.

If a machine cannot reach the registry, it blocks every MCP server it would start. A registry on a private network therefore allows only local MCP servers in CLIs and runners on that network. Remote MCP servers and orb threads stay blocked until ampcode.com and the orb can reach the registry.

Package Matching

For local stdio servers, Amp matches the package name and registry type. Registry approval applies to the package name, not a specific version. A tag, fixed version, version range, or Python extra still matches the same approved package.

Amp supports npm packages run with npx, npm exec, npm x, pnx, pnpx, pnpm dlx, bunx, bun x, or yarn dlx. It supports Python packages run with uvx, uv tool run, or pipx run. Package source options such as uvx --from, pipx run --spec, and bunx --package are supported when the package and command names differ.

Amp blocks package references that do not identify a registry package. It also blocks runner options known to add packages, such as uvx --with, as well as alternate package registries and indexes, shell execution modes, npm aliases, direct URLs, version control sources, archives, and local paths. Other runner options are allowed for compatibility.

Set the registry URL:

  1. Open workspace settings and find MCP Registry.
  2. Enter the registry URL (the v0.1/servers endpoint) and save.

Optionally limit to specific users:

  1. Switch Apply To to Specific users only.
  2. Enter workspace member emails (one per line or comma-separated) and save.

Notes:

  • If you scope to specific users, only those users are restricted by the registry; everyone else is unaffected.
  • Clear the URL to remove the registry and allow all MCP servers.