A side-by-side look at the APICK AI 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 APICK AI for conversational ai work over a hosted endpoint; choose MCP Server Gemini Bridge for conversational ai as a local process. You can also run both side by side in one mcpServers block.
GOOGLE_API_KEY.Rows where the two servers differ are marked.
| Spec | A APICK AI | |
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 36/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | GOOGLE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View APICK AI | View MCP Server Gemini Bridge |
No tool names declared yet. Check the project README from the listing page.
No 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": {
"apick-ai": {
"url": "https://apick.app/dev_guide/mcp"
}
}
}
{
"mcpServers": {
"jaspertvdm-mcp-server-gemini-bridge": {
"command": "uvx",
"args": [
"mcp-server-gemini-bridge"
],
"env": {
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
}
}
}
}