Client-side controls decide which MCP servers can start and which of their tools may run without approval. Claude Code, Codex, Gemini CLI, Cursor and GitHub Copilot all support allowlists by server or tool, and some match on server identity, not just name. Enterprise allowlists stop users from wiring in arbitrary servers from the internet.
Read in this order
- OfficialClaude Code: Control MCP server access for your organizationStart here: how to lock down which MCP servers an org allows.
- OfficialCodex: Managed configuration (MCP allowlist)Codex's MCP allowlist inside its managed configuration.
- OfficialGitHub: Restrict MCP server access to a custom registryRestricting Copilot to a custom MCP registry, step by step.