MCP and Channels Settings

These keys decide which MCP servers and channels Claude Code may use. An MCP server gives Claude extra tools. A channel is a plugin that can push messages into a session. Administrators use these keys to allow or block servers.

Allow and block lists need a managed source to bind users. enableAllProjectMcpServers, disableClaudeAiConnectors, and channelsEnabled are switches.

Keys

Source: Settings Reference for rows marked

Documented: An official docs page names this item.

. For rows marked

Undocumented: Only the program shows this item. It can change without notice.

, Source: the program (its bundled settings schema). Where to Set It tells you which files may set the key. See Settings Files and Scopes.

Key	Status	Type	Default	What It Does	Where to Set It
allowAllClaudeAiMcps	Documented: An official docs page names this item. Managed Only: Works only in managed (organization policy) settings.	boolean	-	Load the claude.ai connectors Claude Code fetches itself alongside a deployed managed-mcp.json. It is off by default. This keeps the lockdown.	Managed settings only
allowClaudeInChromeWithManagedMcp	Documented: An official docs page names this item. Managed Only: Works only in managed (organization policy) settings.	boolean	-	Let the built-in Claude in Chrome server run alongside a deployed managed-mcp.json. This key works in device managed settings only. deniedMcpServers and the organization Chrome setting still block it.	Managed settings only
allowedChannelPlugins	Documented: An official docs page names this item.	array	-	Replace the default allowlist of channel plugins that can push messages. Needs channelsEnabled: true.	Managed settings only
allowedMcpServers	Documented: An official docs page names this item.	array	-	Allowlist which MCP servers users can add. Each entry has exactly one of serverName, serverCommand (an exact array), or serverUrl (a wildcard pattern such as https://*.example.com/*). Not set means allow all. Servers from managedMcpServers and managed-mcp.json entries with no ${VAR} in command, args, url, or header values load without being listed. An entry with ${VAR} in any of those must match the list. Since 2.1.305, a managed-mcp.json stdio server that uses ${VAR} only in env is no longer filtered (v2.1.305 release); use deniedMcpServers to keep one off.	Any settings file
allowManagedMcpServersOnly	Documented: An official docs page names this item. Managed Only: Works only in managed (organization policy) settings.	boolean	-	Make the managed MCP allowlist the only one that applies. deniedMcpServers still merges from all sources. Users can still add servers, but only the admin allowlist applies.	Managed settings only
channelsEnabled	Documented: An official docs page names this item.	boolean	-	Allow channels for your organization. On Teams and Enterprise it is off by default. On Console it is on by default unless managed settings exist.	Managed settings only
deniedMcpServers	Documented: An official docs page names this item.	array	-	Block specific MCP servers by URL, command, or name. Entries have the same shapes. It applies in all scopes, also for the organization.	Any settings file
disableClaudeAiConnectors	Documented: An official docs page names this item.	boolean	-	Turn off claude.ai connectors so Claude Code doesn't fetch them. true in any source wins. It also stops a claudeai-proxy server from --mcp-config.	Any settings file
disabledMcpjsonServers	Documented: An official docs page names this item.	array of string	-	Reject specific servers from a project's .mcp.json. It blocks in every permission mode and every folder.	Any settings file
enableAllProjectMcpServers	Documented: An official docs page names this item.	boolean	-	Approve every server in project .mcp.json files without a prompt. Claude Code ignores it in an untrusted folder when it comes from the checked-in .claude/settings.json.	Any settings file
enabledMcpjsonServers	Documented: An official docs page names this item.	array of string	-	Approve specific servers from a project's .mcp.json. The same trust rule applies.	Any settings file
managedMcpServers	Documented: An official docs page names this item.	object	-	Provide remote MCP servers to every user alongside the ones they add. It accepts only http and sse servers, keyed by name. The entries cannot hold command, args, env, or headersHelper. They cannot hold ${VAR}. The URL must start with https://. Users cannot remove them. deniedMcpServers still applies.	Managed settings only

Example

Approve Project Servers Except One

This file approves the servers in .mcp.json and rejects the one named risky-server.

.claude/settings.json

{
  "enableAllProjectMcpServers": true,
  "disabledMcpjsonServers": ["risky-server"]
}

Related Pages

• Settings Files and Scopes explains the scopes, precedence, and managed settings.
• Settings Reference is the official page for each key.
• MCP covers servers, config, and runtime.
• Control MCP Server Access for Your Organization is the guide for administrators.
• Plugins and MCP Variables lists the matching variables.