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
Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server, with auth support:
4
6
5
7
**Note: this is a working proof-of-concept** but should be considered **experimental**.
@@ -135,6 +137,16 @@ To bypass authentication, or to emit custom headers on all requests to your remo
135
137
]
136
138
```
137
139
140
+
* To allow connections to servers with self-signed or invalid TLS certificates, add the `--insecure` flag. **⚠️ Warning**: This disables certificate verification and should only be used in development environments or trusted networks. Do not use this flag when connecting to untrusted servers as it makes your connection vulnerable to man-in-the-middle attacks.
141
+
142
+
```json
143
+
"args": [
144
+
"mcp-remote",
145
+
"https://self-signed-server.example.com/sse",
146
+
"--insecure"
147
+
]
148
+
```
149
+
138
150
### Transport Strategies
139
151
140
152
MCP Remote supports different transport strategies when connecting to an MCP server. This allows you to control whether it uses Server-Sent Events (SSE) or HTTP transport, and in what order it tries them.
@@ -271,6 +283,8 @@ this might look like:
271
283
}
272
284
```
273
285
286
+
Alternatively, for development or trusted internal servers with self-signed certificates, you can use the `--insecure` flag to bypass certificate validation entirely. **Note**: This should only be used when you trust the server and network.
287
+
274
288
### Check the logs
275
289
276
290
*[Follow Claude Desktop logs in real-time](https://modelcontextprotocol.io/docs/tools/debugging#debugging-in-claude-desktop)
0 commit comments