feat: a setup guide for MCP servers in Cursor, Codex, VS Code and Gemini CLI - #17
Merged
Merged
Conversation
…ini CLI The MCP guide shows the change to a client configuration once, with Claude Code's file as the example. The part that differs between clients is where the file is, what format it is in, and above all what environment a server is started with, which decides whether the API key reaches the proxy at all. Each of these four now has a page that answers those for that client, from its own documentation, and from its source where the documentation says nothing. - Cursor: servers in `mcp.json` under `mcpServers`, which `wrap` edits. A server gets the environment Cursor was started with, so an exported key arrives after a restart, and `envFile` keeps it out of the shell profile. - Codex: servers in TOML, which `wrap` does not read, so the change is shown by hand. Codex starts a server with a cleared environment and passes back only a short list of variables, so the key is forwarded by name with `env_vars`. Its documentation and its source disagree on the default startup timeout, so the page sets it. - VS Code: servers under `servers`, with `type: stdio`. The file allows comments, which `wrap` refuses with an error rather than rewriting, and `code --add-mcp` adds a wrapped server from the command line. - Gemini CLI: it strips variables named like credentials from a server's inherited environment, and `TYPESAFE_API_KEY` is one, so the key is set in the entry's own `env` as a reference that Gemini CLI fills in from its environment. Every page says the proxy removes its own keys before starting the server behind it, shows how to tell from `agent-chaperone log` that a judgment was made without a model, and says plainly that the client's own shell and file tools are not covered, linking the issue that tracks them. The MCP guide links to all four, and the guides list, the structured data and the IndexNow list include them.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MCP guide shows the change to a client configuration once, with Claude Code's file as the example. The part that differs between clients is where the file is, what format it is in, and above all what environment a server is started with, which decides whether the API key reaches the proxy at all. Each of these four now has a page that answers those for that client, from its own documentation, and from its source where the documentation says nothing.
mcp.jsonundermcpServers, whichwrapedits. A server gets the environment Cursor was started with, so an exported key arrives after a restart, andenvFilekeeps it out of the shell profile.wrapdoes not read, so the change is shown by hand. Codex starts a server with a cleared environment and passes back only a short list of variables, so the key is forwarded by name withenv_vars. Its documentation and its source disagree on the default startup timeout, so the page sets it.servers, withtype: stdio. The file allows comments, whichwraprefuses with an error rather than rewriting, andcode --add-mcpadds a wrapped server from the command line.TYPESAFE_API_KEYis one, so the key is set in the entry's ownenvas a reference that Gemini CLI fills in from its environment.Every page says the proxy removes its own keys before starting the server behind it, shows how to tell from
agent-chaperone logthat a judgment was made without a model, and says plainly that the client's own shell and file tools are not covered, linking the issue that tracks them. The MCP guide links to all four, and the guides list, the structured data and the IndexNow list include them.