A side-by-side look at the Gemini and MCP Server Gemini Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gemini for conversational ai work as a local process; choose MCP Server Gemini Bridge for conversational ai as a local process. You can also run both side by side in one mcpServers block.
GEMINI_API_KEY, GEMINI_MODEL.gemini_ask, gemini_analyze, gemini_chat.GOOGLE_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 48/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | GEMINI_API_KEYGEMINI_MODEL | GOOGLE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Gemini | View MCP Server Gemini Bridge |
gemini_askAsk Gemini a question or give it a taskgemini_analyzeSend code/text for analysis with a specific instructiongemini_chatMulti-turn conversation with full historygemini_modelsList available Gemini modelsNo tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"gemini": {
"command": "npx",
"args": [
"-y",
"claude-gemini-mcp"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"GEMINI_MODEL": "YOUR_GEMINI_MODEL_HERE"
}
}
}
}
{
"mcpServers": {
"jaspertvdm-mcp-server-gemini-bridge": {
"command": "uvx",
"args": [
"mcp-server-gemini-bridge"
],
"env": {
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
}
}
}
}