You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/customize/deep-dives/mcp.mdx
+2-49Lines changed: 2 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,56 +72,9 @@ You can set up an MCP server to search the Continue documentation directly from
72
72
73
73
For complete setup instructions, troubleshooting, and usage examples, see the [Continue MCP Reference](/reference/continue-mcp).
74
74
75
-
## How to Configure MCP Servers with JSON Files
75
+
## Using `.mcp.json` from Claude, Cursor, Cline, etc
76
76
77
-
In addition to YAML configuration, you can now configure MCP servers using JSON files. This feature allows you to use Claude-style MCP configurations and provides lower friction when migrating from other tools.
78
-
79
-
### JSON Configuration Options
80
-
81
-
You can create JSON configuration files in the `.continue/mcpServers` folder in two formats:
82
-
83
-
#### Single MCP Server Configuration
84
-
85
-
Create a JSON file where the filename becomes the server name:
JSON configurations support environment variable templating using the `${VAR_NAME}` syntax, which is automatically converted to Continue's `${{ secrets.VAR_NAME }}` format internally.
77
+
If you have an existing `.mcp.json` file from Claude, Cursor, Cline, or any other agent that supports the spec, copy it into your `.continue/mcpServers` directory and Continue will automatically pick it up.
0 commit comments