Skip to content

Commit 86fe33d

Browse files
sestinjContinue
andcommitted
docs: add MCP JSON server configuration support
- Added comprehensive documentation for MCP JSON configuration files - Support for single server and Claude-style multi-server JSON formats - Updated Quick Start section with YAML/JSON tabs - Added environment variable templating documentation - References PR #7956 which added JSON MCP support Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <[email protected]>
1 parent 7d98164 commit 86fe33d

File tree

1 file changed

+66
-3
lines changed

1 file changed

+66
-3
lines changed

docs/customize/deep-dives/mcp.mdx

Lines changed: 66 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,14 @@ explore available MCP server blocks
2727

2828
## Quick Start: How to Set Up Your First MCP Server
2929

30-
Below is a quick example of setting up a new MCP server for use in your agent:
30+
Below is a quick example of setting up a new MCP server for use in your agent. You can use either YAML or JSON configuration files:
3131

3232
1. Create a folder called `.continue/mcpServers` at the top level of your workspace
33-
2. Add a file called `playwright-mcp.yaml` to this folder.
34-
3. Write the following contents to `playwright-mcp.yaml` and save.
33+
2. Add a file called `playwright-mcp.yaml` (or `playwright-mcp.json`) to this folder.
34+
3. Write the following contents to your configuration file and save.
3535

36+
<Tabs>
37+
<Tab title="YAML">
3638
```yaml title=".continue/mcpServers/playwright-mcp.yaml"
3739
name: Playwright mcpServer
3840
version: 0.0.1
@@ -43,6 +45,16 @@ mcpServers:
4345
args:
4446
- "@playwright/mcp@latest"
4547
```
48+
</Tab>
49+
<Tab title="JSON">
50+
```json title=".continue/mcpServers/playwright-mcp.json"
51+
{
52+
"command": "npx",
53+
"args": ["@playwright/mcp@latest"]
54+
}
55+
```
56+
</Tab>
57+
</Tabs>
4658

4759
Now test your MCP server by prompting the following command:
4860

@@ -60,6 +72,57 @@ You can set up an MCP server to search the Continue documentation directly from
6072

6173
For complete setup instructions, troubleshooting, and usage examples, see the [Continue MCP Reference](/reference/continue-mcp).
6274

75+
## How to Configure MCP Servers with JSON Files
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:
86+
87+
```json title=".continue/mcpServers/my-server.json"
88+
{
89+
"command": "npx",
90+
"args": ["-y", "@modelcontextprotocol/server-sqlite"],
91+
"env": {
92+
"DATABASE_PATH": "${DATABASE_PATH}"
93+
}
94+
}
95+
```
96+
97+
#### Claude-style MCP Server Configuration
98+
99+
Create a JSON file with multiple servers using the `mcpServers` format:
100+
101+
```json title=".continue/mcpServers/claude-style.json"
102+
{
103+
"mcpServers": {
104+
"sqlite": {
105+
"command": "npx",
106+
"args": ["-y", "@modelcontextprotocol/server-sqlite"],
107+
"env": {
108+
"DATABASE_PATH": "${DATABASE_PATH}"
109+
}
110+
},
111+
"github": {
112+
"command": "npx",
113+
"args": ["-y", "@modelcontextprotocol/server-github"],
114+
"env": {
115+
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
116+
}
117+
}
118+
}
119+
}
120+
```
121+
122+
### Environment Variable Templating
123+
124+
JSON configurations support environment variable templating using the `${VAR_NAME}` syntax, which is automatically converted to Continue's `${{ secrets.VAR_NAME }}` format internally.
125+
63126
## How to Configure MCP Servers
64127

65128
To set up your own MCP server, read the [MCP

0 commit comments

Comments
 (0)