gemini-mcp-server
Related Servers
Alternatives to gemini-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Gemini AI models through MCP protocol. Provides text generation capabilities with configurable model selection and temperature settings.62 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP clients to Gemini Cloud Assist APIs, enabling users to understand, manage, and troubleshoot their Google Cloud environment using natural language.69Apache 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
- AlicenseAqualityDmaintenanceMCP server that completes prompts with automatic provider fallback across OpenAI, Anthropic Claude, and Google Gemini. It is rate-limit aware, retries on transient failures, and provides a transparent attempt log.210 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables users to ask questions answered through the Google Gemini REST API's generateContent endpoint, exposed as a single tool that accepts a prompt plus optional model, temperature, and token-limit settings. It runs locally over stdio and can be wired into LM Studio, returning network, auth, timeout, and invalid-response failures as readable tool errors.-
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.