gemini-mcp-server
Related Servers
Alternatives to gemini-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to consult Google Gemini through a single tool that returns text answers, with automatic retries, exponential backoff, and fallback across models for rate limits or outages.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Gemini AI models through MCP protocol. Provides text generation capabilities with configurable model selection and temperature settings.285 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to submit prompts and optional context to a signed-in Gemini Web tab through browser CDP and receive a newly completed assistant response when the expected model setting is active.MIT
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients to Gemini Cloud Assist APIs, enabling users to understand, manage, and troubleshoot their Google Cloud environment using natural language.72Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMinimal MCP server that provides access to Google's Gemini API with Google Search grounding for up-to-date information through a single ask_gemini tool.MIT
- AlicenseAqualityCmaintenanceExposes a single chat tool that lets any MCP client send text prompts together with images, PDFs, or Office attachments to a self-hosted Gemini web endpoint and get OpenAI-compatible responses back. An optional companion checker keeps the underlying Google session cookies fresh automatically so requests keep working without manual re-authentication.1MIT
TDQS
Scored across 1 tool
With only a single tool (gemini_ask), there is no possibility of confusing it with another tool. Its purpose—send a prompt to Gemini and return the answer—is unambiguous.
The lone name gemini_ask follows a clean snake_case verb_noun pattern and is fully self-consistent. There are no competing conventions to create inconsistency.
A one-tool surface is thin for a server, even though asking Gemini is genuinely the core capability. The rubric treats a single tool as borderline, and there is no supporting surface (e.g. conversation or model listing).
The basic one-shot question/answer flow is covered, including model and system-instruction options. However, there is no multi-turn conversation, model discovery, or other lifecycle operations, leaving notable gaps for a general Gemini integration.