enterprise_management
Whether the provider supports organization-level MCP configuration management, including managed server lists, allowlists, and enterprise registries.
Type: bool Content type: mcp
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| amp | ✓ | enterprise_registry_allowlist: Amp supports organization-level MCP configuration with an enterprise registry and allowlist |
| claude-code | ✓ | mcp_managed_config: managed-mcp.json for exclusive control, or allowedMcpServers/deniedMcpServers in managed settings for policy-based control |
| opencode | ✓ | Organizations can provide default MCP server configurations via a .well-known/opencode endpoint; users can override remote defaults in their local opencode.json; local config values take precedence over remote defaults |
| windsurf | ✓ | enterprise_whitelist_and_registry: Windsurf supports organization-level MCP server allowlists and enterprise registries |
| cline | ✗ | Cline does not document organization-level MCP configuration management |
| codex | ✗ | Codex does not document organization-level MCP management |
| copilot-cli | ✗ | Copilot CLI does not document organization-level MCP management |
| crush | ✗ | Crush does not document organization-level MCP management |
| cursor | ✗ | Cursor does not document organization-level managed MCP policy controls beyond the general hook and rule enterprise scopes. |
| factory-droid | ✗ | only user-level (~/.factory/mcp.json) and project-level (.factory/mcp.json) configuration scopes documented; no organization/enterprise admin layer |
| gemini-cli | ✗ | Gemini CLI does not document organization-level MCP management |
| kiro | ✗ | Kiro does not document organization-level MCP management |
| pi | ✗ | not documented |
| roo-code | ✗ | No organization-level MCP management documented |
| zed | ✗ | Zed does not document org-level MCP management |