wrap.
- {' '}
- Wrap a server Cursor reaches by URL by hand instead, as{' '}
- the MCP guide shows, and pass any token it needs
- with --header-env. Headers written in the Cursor entry stay with Cursor and
- never reach the proxy.
+ A server that authenticates with headers. Headers written in the Cursor entry stay
+ with Cursor and never reach the proxy, which is why wrap, from 0.3.2, leaves
+ such an entry alone. Put it behind the proxy by hand, as{' '}
+ the MCP guide shows, and pass the token with{' '}
+ --header-env.
+ wrap treats a{' '}
+ url entry as Streamable HTTP, the only transport the proxy reaches a URL over,
+ so a server that answers over SSE alone will not connect once wrapped.
agent-chaperone wrap ~/.gemini/settings.json can make the command change, but not
the env line, which you add afterwards. It reads the file as strict JSON, and
Gemini CLI allows comments in its settings, so a file with comments is refused with an error
- and left untouched. It also wraps every server in the file, so use it on a file whose servers
- all run a local command.
+ and left untouched. Leave remote servers out of it: in Gemini CLI a url entry
+ means the older SSE transport and httpUrl means Streamable HTTP, and{' '}
+ wrap skips httpUrl entries and would treat a url entry
+ as Streamable HTTP.
@@ -145,10 +147,11 @@ const guide = findGuide('gemini-cli');
those does not exist yet.
--header-env: headers written in the Gemini CLI entry never reach the
- proxy.
+ A server Gemini CLI reaches by URL. Put an httpUrl server behind the
+ proxy by hand, as the MCP guide shows, with the URL
+ after --, and pass any token it needs with --header-env: headers
+ written in the Gemini CLI entry never reach the proxy. A url server speaks SSE,
+ and the proxy reaches a URL over Streamable HTTP only.
--server names the section of the policy file that applies.
- agent-chaperone wrap can make the edit, with two limits on VS Code. It reads the
- file as strict JSON, and VS Code allows comments in mcp.json, so a file with
- comments is refused with an error and left untouched. And it wraps every server in the file,
- so use it on a file whose servers all run a local command. Otherwise edit the entry by hand as
- above.
+ agent-chaperone wrap can make the edit. It reads the file as strict JSON, and VS
+ Code allows comments in mcp.json, so a file with comments is refused with an
+ error and left untouched; edit that one by hand as above. A server VS Code reaches by URL is
+ wrapped too, from 0.3.2, with its type changed from http to{' '}
+ stdio because the entry now runs a command, and --unwrap changes it
+ back. One that carries its own headers, or declares the older SSE transport, is
+ left alone and the output says why.
agent-chaperone wrap .vscode/mcp.json
agent-chaperone wrap .vscode/mcp.json --writetype set to{' '}
- stdio, since the entry now runs a command. Pass any token it needs with{' '}
- --header-env: headers written in the VS Code entry never reach the proxy.
+ A server that authenticates with headers. Headers written in the VS Code entry never
+ reach the proxy, which is why wrap leaves such an entry alone. Put it behind
+ the proxy by hand, as the MCP guide shows, with{' '}
+ type set to stdio, and pass the token with{' '}
+ --header-env.
+