gemini-mcp
Related Servers
Alternatives to gemini-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.9 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP clients like Codex to operate chatgpt.com through a dedicated persistent browser profile, allowing chat creation, project management, prompt submission, file uploads, and response reading without using the ChatGPT API.33MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to drive ChatGPT's web interface through a built-in persistent browser, requiring only a single manual login. Prompts are sent through temporary incognito chats and the captured answer text is returned as tool results, along with live model listing, login/status probing, and optional HTTP transport.83Apache 2.0
- AlicenseBqualityCmaintenanceEnables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.7GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.8 npm-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.23 npmApache 2.0
TDQS
Scored across 6 tools
Each tool has a distinct role: status vs usage are separated by session/model info versus quota/limits, and chat/new_chat/switch_model/upload_and_ask are clearly differentiated. The only mild overlap is between gemini_chat and gemini_upload_and_ask, since both send prompts, but the file-upload capability makes the boundary clear enough.
All six tools use a consistent gemini_ prefix with snake_case verb/noun naming (gemini_status, gemini_chat, gemini_new_chat, gemini_usage, gemini_switch_model, gemini_upload_and_ask). The pattern is predictable and readable throughout.
Six tools is well-scoped for a Gemini web-session wrapper, with each tool earning its place across status, chat, reset, usage, model switching, and file upload. There is no obvious redundancy or bloat.
The surface covers the core lifecycle: check status, start a new chat, send prompts, switch models, upload files, and inspect usage. Minor gaps exist around conversation history management (listing or deleting past chats), but core workflows are covered.