F
licenseA
qualityD
maintenanceWraps Google Gemini's image generation API as an MCP server, enabling text-to-image, image editing, and grounded search workflows from any MCP client.
2
-
gemini-mcp
by chrischall
Related Servers
Alternatives to gemini-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceRemote MCP server that exposes Google Gemini's text, image, video (Veo), and audio transcription capabilities as tools any MCP client can call directly.95 npmMIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server exposing MiniMax's image, speech, music, and video generation APIs as MCP tools for use with any MCP-aware host.4,211 npmMIT
- FlicenseAqualityCmaintenanceMCP server that wraps MiniMax platform APIs (speech, video, image, music, and file management) as tools over stdio, enabling natural language interaction with MiniMax's AI services.161-
- FlicenseNot gradedqualityCmaintenanceAn MCP server for generating and editing images with Google's Gemini image models, exposing a single tool that AI assistants can call to create or edit images using your own API key.1-
- AlicenseAqualityFmaintenanceProduction-grade MCP server for image and video understanding and generation across Gemini, OpenAI, and Grok.5140 PyPI4Apache 2.0
TDQS
A4.3/5.0
Scored across 13 tools
Disambiguation3/5
The four image-related tools (gemini_image_generate, gemini_image_edit, gemini_image_set, gemini_interact) have overlapping purposes, though the detailed descriptions with cross-references help guide selection. The other tools are clearly distinct, so the set is not highly ambiguous, but agents may still struggle to choose the right image tool at first.
Naming Consistency3/5
All tools share a consistent 'gemini_' prefix and snake_case, but the word order is mixed: some use verb_noun (list_models, upload_file), others noun_verb (image_generate, music_generate), and a few are compound nouns or bare verbs (healthcheck, interact). This mixed convention is readable but not uniform.
Tool Count5/5
13 tools is well within the ideal 3-15 range for a media generation server. Each tool covers a distinct part of the workflow: generation, editing, async retrieval, file management, model listing, health check, and usage tracking. No tool feels redundant or missing.
Completeness5/5
The tool surface covers the full lifecycle for media generation: create (image/video/music), edit, refine, set generation, async results, file upload/list/delete, model listing, and cost tracking. There are no obvious dead ends or critical missing operations for the stated purpose.
Maintenance
ActivityActive
ResponsivenessResponsive