MCP Config Lab
Gemini CLI guide

Generate a Gemini CLI
MCP config.

Convert MCP servers from Claude, Cursor, Codex, VS Code or Windsurf into Gemini CLI’s settings.json shape.

Gemini CLI MCP configuration

Gemini CLI defines servers inside an mcpServers object. Local servers use command and args; remote servers commonly use httpUrl. MCP Config Lab normalizes the source format and emits the Gemini field names.

{
  "mcpServers": {
    "docs": {
      "httpUrl": "https://mcp.example.com/mcp",
      "headers": {
        "Authorization": "Bearer ${DOCS_TOKEN}"
      }
    }
  }
}
Generate Gemini config →

Local and remote transports

For a local stdio server, keep the executable in command and each argument as a separate item in args. For a remote server, use a secure HTTPS endpoint and pass credentials as environment-variable references where supported.

Keep configs portable

Avoid editor-specific workspace variables when a configuration will be shared across clients. The converter reports fields such as Cursor’s envFile or Cline permissions instead of silently pretending every client supports them.