Skip to main content
Glama
sanxfxteam

Gemini MCP Image Generation Server

by sanxfxteam

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

  1. Obtener la clave API de Gemini

  2. 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.json
    • Agregar configuración de Gemini:

      {
        "mcpServers": {
          "gemini-imagen": {
            "command": "npx",
            "args": ["-y", "github:sanxfxteam/gemini-mcp-server"],
            "env": {
              "GEMINI_API_KEY": "your_api_key_here"
            }
          }
        }
      }
  3. Reiniciar Claude Desktop

Related MCP server: Image Toolkit MCP Server

Configuración

  1. Instalar dependencias:

npm install
  1. Configura tus variables de entorno: crea un archivo .env en el directorio raíz y agrega tu clave API de Google:

GEMINI_API_KEY=your_api_key_here

Uso

Ejecutar el servidor:

npm start

Para probar

npx @modelcontextprotocol/inspector npm run start

Herramientas 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 generar

  • numSamples (número, opcional, predeterminado: 4): Número de imágenes a generar

  • aspectRatio (cadena, opcional, valor predeterminado: '1:1'): Relación de aspecto de las imágenes generadas

  • personGeneration (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 tool
generateImageD
ParametersJSON Schema
NameRequiredDescriptionDefault
aspectRatioNo
outputFormatNo
promptYes

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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. 1 tool updatev1.0.0
    • First observedgenerateImage

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generateImage' stands alone with a distinct purpose.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers