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
Add a remote-server section and type/url/headers fields to the MCP
configuration guide (zh + en, docs and bundled skill references), and
note remote support in the README MCP FAQ.
Copy file name to clipboardExpand all lines: README-en.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,7 +133,7 @@ Yes. Just set `env.BASE_URL` in `~/.deepcode/settings.json` to an OpenAI-compati
133
133
134
134
### How do I configure MCP?
135
135
136
-
Deep Code supports MCP (Model Context Protocol) to connect external services such as GitHub, browsers, databases, and more. Configure the `mcpServers` field in `settings.json` to enable it, then use the `/mcp` command to view MCP server status and available tools.
136
+
Deep Code supports MCP (Model Context Protocol) to connect external services such as GitHub, browsers, databases, and more. Configure the `mcpServers` field in `settings.json` to enable it — both local stdio servers and remote Streamable HTTP servers are supported — then use the `/mcp` command to view MCP server status and available tools.
137
137
138
138
For detailed setup instructions, see: [docs/mcp.md](docs/mcp.md)
|`command`| string |Yes| Path or command of the MCP server executable (e.g., `npx`, `node`, `python`). When the command is `npx`, Deep Code automatically prepends `-y` to the arguments. |
46
+
|`command`| string |No| Executable path or command for a local stdio server (e.g., `npx`, `node`, `python`). When the command is `npx`, Deep Code automatically prepends `-y` to the arguments. |
47
47
|`args`| string[]| No | List of arguments to pass to the command |
48
48
|`env`| object | No | Environment variables (e.g., API keys) to pass to the MCP server process |
49
+
|`type`| string | No | Transport: `stdio` (local subprocess, default) or `http` (remote Streamable HTTP). Defaults to `http` when a `url` is given. |
50
+
|`url`| string | No | HTTP(S) endpoint of a remote MCP server (Streamable HTTP). When set, the server is remote and no `command` is needed. |
51
+
|`headers`| object | No | HTTP headers (e.g., `Authorization`) sent with each remote request, typically for authentication. |
52
+
53
+
> Use `command`/`args`/`env` for local servers, or `url`/`headers` for remote servers — one or the other.
54
+
55
+
## Remote MCP Servers (Streamable HTTP)
56
+
57
+
In addition to local stdio servers, Deep Code can connect to remote MCP servers over **Streamable HTTP** (MCP 2025-03-26). Just provide a `url` (or set `type: "http"` explicitly):
58
+
59
+
```json
60
+
{
61
+
"mcpServers": {
62
+
"remote-service": {
63
+
"type": "http",
64
+
"url": "https://example.com/mcp",
65
+
"headers": {
66
+
"Authorization": "Bearer <token>"
67
+
}
68
+
}
69
+
}
70
+
}
71
+
```
72
+
73
+
-`url`: the remote server's HTTP(S) endpoint.
74
+
-`headers`: optional HTTP headers attached to every request, typically for authentication (e.g., `Authorization`).
75
+
- The `Mcp-Session-Id` returned by the server on initialize is captured automatically and echoed on subsequent requests.
76
+
77
+
> Only Streamable HTTP is supported for now; the legacy two-endpoint HTTP+SSE transport and OAuth authorization flows are not yet handled.
|`command`| string |Yes| Path or command of the MCP server executable (e.g., `npx`, `node`, `python`). When the command is `npx`, Deep Code automatically prepends `-y` to the arguments. |
46
+
|`command`| string |No| Executable path or command for a local stdio server (e.g., `npx`, `node`, `python`). When the command is `npx`, Deep Code automatically prepends `-y` to the arguments. |
47
47
|`args`| string[]| No | List of arguments to pass to the command |
48
48
|`env`| object | No | Environment variables (e.g., API keys) to pass to the MCP server process |
49
+
|`type`| string | No | Transport: `stdio` (local subprocess, default) or `http` (remote Streamable HTTP). Defaults to `http` when a `url` is given. |
50
+
|`url`| string | No | HTTP(S) endpoint of a remote MCP server (Streamable HTTP). When set, the server is remote and no `command` is needed. |
51
+
|`headers`| object | No | HTTP headers (e.g., `Authorization`) sent with each remote request, typically for authentication. |
52
+
53
+
> Use `command`/`args`/`env` for local servers, or `url`/`headers` for remote servers — one or the other.
54
+
55
+
## Remote MCP Servers (Streamable HTTP)
56
+
57
+
In addition to local stdio servers, Deep Code can connect to remote MCP servers over **Streamable HTTP** (MCP 2025-03-26). Just provide a `url` (or set `type: "http"` explicitly):
58
+
59
+
```json
60
+
{
61
+
"mcpServers": {
62
+
"remote-service": {
63
+
"type": "http",
64
+
"url": "https://example.com/mcp",
65
+
"headers": {
66
+
"Authorization": "Bearer <token>"
67
+
}
68
+
}
69
+
}
70
+
}
71
+
```
72
+
73
+
-`url`: the remote server's HTTP(S) endpoint.
74
+
-`headers`: optional HTTP headers attached to every request, typically for authentication (e.g., `Authorization`).
75
+
- The `Mcp-Session-Id` returned by the server on initialize is captured automatically and echoed on subsequent requests.
76
+
77
+
> Only Streamable HTTP is supported for now; the legacy two-endpoint HTTP+SSE transport and OAuth authorization flows are not yet handled.
0 commit comments