Gemini CLI supports remote MCP over Streamable HTTP with OAuth. Gemini web custom apps are a separate account-dependent path; neither client has a live Studio verification in this release.
Choose a fixed callback port, add http://localhost:8765/oauth/callback to Studio, and use the matching redirectUri in the CLI configuration. Keep the endpoint HTTPS; only the browser’s callback uses loopback HTTP.
{
"mcpServers": {
"wpbridge-studio": {
"httpUrl": "https://YOUR-SITE/wp-json/wpbridge-studio/v1/mcp",
"oauth": {
"enabled": true,
"scopes": [
"wordpress",
"offline_access"
],
"redirectUri": "http://localhost:8765/oauth/callback"
}
}
}
}
Use /mcp auth to authorize, then inspect discovered tools. Do not mark all tools trusted automatically. See Google’s official MCP documentation.
Google documents adding custom MCP apps in Gemini web. Feature availability varies by account and region. Confirm access to custom apps, then use the exact callback supplied by Gemini; Studio intentionally does not guess or broadly allow Google callback URLs.
Google’s custom app instructions describe the client-side flow. Record a successful site_status and read test before treating the connection as verified.