MCP Registry Allowlist

Enterprise workspace admins can enforce an MCP registry so that only approved MCP servers are available to workspace members. If the registry is unreachable, all MCP servers are blocked. The registry protocol and schema are defined at registry.modelcontextprotocol.io.

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.