docs/enterprise-solutions/configuration/infrastructure-configuration/control-other-cline-features/mcp-marketplace.mdx
The MCP Marketplace lets developers discover and install MCP servers that extend Cline's capabilities. For Enterprise administrators, this page covers how to control marketplace access, restrict which servers are available, and push pre-configured MCP servers to your organization.
<Note> For complete details about the MCP Marketplace and how developers use it, see [MCP Made Easy](/mcp/mcp-marketplace). </Note>Enterprise administrators have four configuration options to govern MCP server usage across their organization:
| Setting | Purpose |
|---|---|
mcpMarketplaceEnabled | Enable or disable the MCP Marketplace entirely |
allowedMCPServers | Restrict the marketplace to only approved MCP servers |
remoteMCPServers | Push pre-configured remote MCP servers to all users |
blockPersonalRemoteMCPServers | Prevent users from adding their own remote MCP servers |
These settings are applied through your organization's remote configuration and take effect immediately for all team members.
To completely disable the MCP Marketplace for your organization, set mcpMarketplaceEnabled to false:
{
"mcpMarketplaceEnabled": false
}
When mcpMarketplaceEnabled is set to false:
When mcpMarketplaceEnabled is set to true or omitted:
Rather than disabling the marketplace entirely, you can restrict it to a curated list of approved MCP servers using the allowedMCPServers setting. This is the recommended approach for most enterprises — it lets developers benefit from MCP while ensuring only vetted servers are available.
Add an allowedMCPServers array to your remote configuration. Each entry requires an id field set to the server's GitHub repository path:
{
"allowedMCPServers": [
{ "id": "github.com/modelcontextprotocol/server-filesystem" },
{ "id": "github.com/modelcontextprotocol/server-github" },
{ "id": "github.com/your-org/internal-mcp-server" }
]
}
When allowedMCPServers is configured:
When allowedMCPServers is omitted or undefined:
When allowedMCPServers is set to an empty array ([]):
The id for each allowed server is its GitHub repository path (without the https:// prefix). For example:
| Server | ID |
|---|---|
| Filesystem | github.com/modelcontextprotocol/server-filesystem |
| GitHub | github.com/modelcontextprotocol/server-github |
| Custom internal server | github.com/your-org/your-mcp-server |
You can find the correct ID by checking the githubUrl field of any server in the MCP Marketplace and removing the https:// prefix.
Use remoteMCPServers to push MCP servers directly to all users without requiring them to install anything from the marketplace. This is ideal for internal MCP servers or third-party servers that need specific configuration.
{
"remoteMCPServers": [
{
"name": "Internal Code Search",
"url": "https://mcp.internal.yourcompany.com/code-search",
"alwaysEnabled": true,
"headers": {
"Authorization": "Bearer ${AUTH_TOKEN}"
}
},
{
"name": "Documentation Server",
"url": "https://mcp.internal.yourcompany.com/docs",
"alwaysEnabled": false
}
]
}
Each remote MCP server entry supports the following fields:
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Display name for the server |
url | string | Yes | The URL endpoint of the MCP server |
alwaysEnabled | boolean | No | When true, users cannot disable this server |
headers | object | No | Custom HTTP headers for authentication |
When alwaysEnabled is set to true:
To prevent users from adding their own remote MCP servers, set blockPersonalRemoteMCPServers to true:
{
"blockPersonalRemoteMCPServers": true
}
When blockPersonalRemoteMCPServers is true:
remoteMCPServers configuration are availableWhen blockPersonalRemoteMCPServers is false or omitted:
For organizations that need strict control over all MCP server access:
{
"mcpMarketplaceEnabled": true,
"allowedMCPServers": [
{ "id": "github.com/modelcontextprotocol/server-filesystem" },
{ "id": "github.com/modelcontextprotocol/server-github" }
],
"remoteMCPServers": [
{
"name": "Internal API Gateway",
"url": "https://mcp.internal.yourcompany.com/gateway",
"alwaysEnabled": true,
"headers": {
"X-Api-Key": "org-managed-key"
}
}
],
"blockPersonalRemoteMCPServers": true
}
This configuration:
For organizations that want flexibility with internal server access:
{
"remoteMCPServers": [
{
"name": "Company Knowledge Base",
"url": "https://mcp.yourcompany.com/kb",
"alwaysEnabled": true
}
]
}
This configuration:
allowedMCPServers restriction)For organizations that want to fully manage the MCP experience:
{
"mcpMarketplaceEnabled": false,
"remoteMCPServers": [
{
"name": "Approved Code Assistant",
"url": "https://mcp.internal.yourcompany.com/code-assist",
"alwaysEnabled": true
},
{
"name": "Internal Docs Search",
"url": "https://mcp.internal.yourcompany.com/docs",
"alwaysEnabled": true
}
],
"blockPersonalRemoteMCPServers": true
}
This configuration:
Most organizations should use the allowlist (allowedMCPServers) rather than disabling the marketplace entirely. This gives developers access to useful tools while ensuring security review of each server.
alwaysEnabledblockPersonalRemoteMCPServers: true)blockPersonalRemoteMCPServers: true)For help configuring MCP Marketplace policies: