Gemini MCP Image Generation Server
Servidor MCP de generación de imágenes Gemini
Este es un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona capacidades de generación de imágenes mediante la API Gemini 2 de Google.
Inicio rápido
Obtener la clave API de Gemini
Visita Google AI Studio
Crear una nueva clave API
Configurar Claude Desktop
Localice su archivo de configuración:
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json Linux: ~/.config/Claude/claude_desktop_config.jsonAgregar configuración de Gemini:
{ "mcpServers": { "gemini-imagen": { "command": "npx", "args": ["-y", "github:sanxfxteam/gemini-mcp-server"], "env": { "GEMINI_API_KEY": "your_api_key_here" } } } }
Reiniciar Claude Desktop
Related MCP server: Image Toolkit MCP Server
Configuración
Instalar dependencias:
npm installConfigura tus variables de entorno: crea un archivo
.enven el directorio raíz y agrega tu clave API de Google:
GEMINI_API_KEY=your_api_key_hereUso
Ejecutar el servidor:
npm startPara probar
npx @modelcontextprotocol/inspector npm run startHerramientas disponibles
generarImagen
Genera imágenes utilizando la API de generación de imágenes experimental de Gemini 2.
Parámetros:
prompt(cadena, obligatorio): La descripción de la imagen que desea generarnumSamples(número, opcional, predeterminado: 4): Número de imágenes a generaraspectRatio(cadena, opcional, valor predeterminado: '1:1'): Relación de aspecto de las imágenes generadaspersonGeneration(cadena, opcional, valor predeterminado: 'ALLOW_ADULT'): Configuración de generación de personas
Ejemplo de solicitud MCP:
{
"tool": "generateImage",
"params": {
"prompt": "A serene mountain landscape at sunset",
"numSamples": 2,
"aspectRatio": "16:9"
}
}Notas
Este servidor utiliza la función de generación de imágenes experimentales de Gemini 2
Asegúrate de tener el acceso y las claves API adecuadas de Google
El servidor se comunica utilizando el Protocolo de Contexto de Modelo a través de stdio
Available Tools
1 toolgenerateImageD
| Name | Required | Description | Default |
|---|---|---|---|
| aspectRatio | No | ||
| outputFormat | No | ||
| prompt | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
generateImage
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generateImage' stands alone with a distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'generateImage' follows a clear verb_noun pattern.
One tool is too few for a server named 'Gemini MCP Image Generation Server', which suggests a broader scope for image generation tasks. A single tool feels thin and incomplete for this domain.
The server is severely incomplete for image generation. It lacks essential operations like listing generated images, editing or modifying images, deleting images, or handling different image formats or styles, leaving significant gaps in functionality.
Maintenance
Related MCP Connectors
Multi-model AI image and video generator. 14 models behind one OAuth-secured MCP endpoint.
MCP server for Google Veo AI video generation
MCP server for Qwen Image 3 AI image generation
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol server that provides image generation capabilities using the Ideogram API, allowing users to create images from text prompts with customizable parameters.116 npm5MIT
- AlicenseNot gradedqualityFmaintenanceA server that provides AI-powered image generation, modification, and processing capabilities through the Model Context Protocol, leveraging Google Gemini models and other image services.18MIT
- AlicenseDqualityFmaintenanceA Model Context Protocol server that enables generating and editing images using OpenAI's gpt-image-1 model, allowing AI assistants to create and modify images from text prompts.2103 npm18MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that connects to Google AI Studio/Gemini API, enabling content generation with support for various file types, conversation history, and system prompts.1120 npm39MIT