docs/mcp/adding-and-configuring-servers.mdx
This guide covers finding MCP servers, adding them to Cline, and configuring their settings.
Several places to find MCP servers:
The easiest way to add an MCP server is to have Cline build it for you:
Example conversation:
User: "Add the MCP server from https://github.com/modelcontextprotocol/servers/tree/main/src/brave-search"
Cline: "Cloning the repository. It needs to be built. Should I run 'npm run build'?"
User: "Yes"
Cline: "Build complete. This server needs an API key. Where should I find it?"
Access server settings through the MCP Servers icon in Cline's top navigation bar.
Toggle the switch next to any server to enable or disable it.
Click "Restart Server" if a server becomes unresponsive.
Click the trash icon or "Delete Server" button. No confirmation dialog.
Set how long to wait for responses (30 seconds to 1 hour, default 1 minute).
Settings are stored in cline_mcp_settings.json:
{
"mcpServers": {
"local-server": {
"command": "node",
"args": ["/path/to/server.js"],
"env": {
"API_KEY": "your_api_key"
},
"alwaysAllow": ["tool1", "tool2"],
"disabled": false
}
}
}
{
"mcpServers": {
"remote-server": {
"url": "https://your-server-url.com/mcp",
"headers": {
"Authorization": "Bearer your-token"
},
"alwaysAllow": ["tool3"],
"disabled": false
}
}
}
Control how MCP servers affect token usage:
Cline>Mcp:Mode and select your preferenceAfter configuring a server, Cline automatically detects available tools:
| Issue | Solution |
|---|---|
| Server not responding | Check if process is running, verify network connectivity |
| Permission errors | Ensure API keys and credentials are configured |
| Tool not available | Confirm server implements the tool and it's not disabled |
| Slow performance | Increase network timeout for the server |