Skip to main content
Glama
enesjakozh
rmcendarfer2017

Image Generator MCP Server

by rmcendarfer2017
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Generador de imágenes del servidor MCP

Un servidor MCP que utiliza Replicate para generar imágenes y permite a los usuarios guardarlas.

Componentes

Recursos

El servidor implementa un sistema de almacenamiento de imágenes con:

  • Imagen personalizada:// Esquema de URI para acceder a imágenes individuales generadas

  • Cada recurso de imagen tiene un nombre basado en su solicitud, una descripción con fecha de creación y un tipo MIME de imagen/png.

Indicaciones

El servidor proporciona un único mensaje:

  • generate-image: Crea indicaciones para generar imágenes usando Stable Diffusion

    • Argumento opcional "estilo" para controlar el estilo de la imagen (realista/artístico/abstracto)

    • Genera una plantilla de solicitud con orientación específica de estilo.

Herramientas

El servidor implementa tres herramientas:

  • generate-image: genera una imagen utilizando el modelo de difusión estable de Replicate

    • Toma "prompt" como un argumento de cadena obligatorio

    • Los parámetros opcionales incluyen "negative_prompt", "width", "height", "num_inference_steps" y "guidance_scale".

    • Devuelve la imagen generada y su URL

  • save-image: guarda una imagen generada en el sistema de archivos local

    • Toma "image_url" y "prompt" como argumentos de cadena obligatorios

    • Genera una identificación única para la imagen y la guarda en el directorio "generated_images"

  • list-saved-images: enumera todas las imágenes guardadas

    • Devuelve una lista de todas las imágenes guardadas con sus metadatos y miniaturas.

Related MCP server: gemini-image-mcp

Configuración

Replicar token de API

Para utilizar este generador de imágenes, necesita un token de API de replicación:

  1. Crea una cuenta en Replicate

  2. Obtenga su token API desde https://replicate.com/account

  3. Cree un archivo .env basado en la plantilla .env.example proporcionada:

REPLICATE_API_TOKEN=your_replicate_api_token_here

Importante: El archivo .env se excluye del control de versiones mediante .gitignore para evitar la exposición accidental de su token de API. Nunca envíe información confidencial a su repositorio.

Configuración del entorno

  1. Clonar el repositorio:

git clone https://github.com/yourusername/image-generator.git
cd image-generator

  1. Crear y activar un entorno virtual:

# Using venv
python -m venv .venv
# On Windows
.venv\Scripts\activate
# On macOS/Linux
source .venv/bin/activate

  1. Instalar dependencias:

pip install -r requirements.txt

  1. Configure su archivo .env como se describe arriba

Inicio rápido

Instalar

Escritorio de Claude

En MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json En Windows: %APPDATA%/Claude/claude_desktop_config.json

Uso

Una vez que el servidor esté en funcionamiento, puedes:

  1. Genere una imagen utilizando la herramienta "generar imagen" con una indicación descriptiva

  2. Guarde la imagen generada usando la herramienta "guardar imagen" con la URL de la imagen y el mensaje

  3. Ver todas las imágenes guardadas usando la herramienta "lista-de-imágenes-guardadas"

  4. Acceda a las imágenes guardadas a través de la lista de recursos

Desarrollo

Construcción y publicación

Para preparar el paquete para su distribución:

  1. Sincronizar dependencias y actualizar el archivo de bloqueo:

uv sync

  1. Distribuciones de paquetes de compilación:

uv build

Esto creará distribuciones de origen y de rueda en el directorio dist/ .

  1. Publicar en PyPI:

uv publish

Nota: Deberás configurar las credenciales de PyPI a través de variables de entorno o indicadores de comando:

  • Token: --token o UV_PUBLISH_TOKEN

  • O nombre de usuario/contraseña: --username / UV_PUBLISH_USERNAME y --password / UV_PUBLISH_PASSWORD

Depuración

Dado que los servidores MCP se ejecutan en stdio, la depuración puede ser complicada. Para una experiencia óptima, recomendamos usar el Inspector MCP .

Puede iniciar el Inspector MCP a través de npm con este comando:

npx @modelcontextprotocol/inspector uv --directory B:\NEWTEST\image-generator run image-generator

Al iniciarse, el Inspector mostrará una URL a la que podrá acceder en su navegador para comenzar a depurar.

Available Tools

3 tools
generate-imageC

Generate an image using Replicate's Stable Diffusion model

ParametersJSON Schema
NameRequiredDescriptionDefault
widthNo
heightNo
promptYes
guidance_scaleNo
negative_promptNo
num_inference_stepsNo

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description alone must disclose behavior. It only states image generation, but omits whether the image is returned directly, saved, or streamed. No mention of rate limits, authentication, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded. However, it might be too terse, sacrificing critical details. Every word earns its place, but more information would improve usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters, no output schema, and no annotations, the description is incomplete. It fails to clarify whether output is a URL, base64, or file path. Critical for an agent to use correctly.

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?

Schema description coverage is 0%, and the description provides no explanation of parameters beyond their existence. Values like 'guidance_scale', 'num_inference_steps', and 'negative_prompt' are left undefined. The agent must infer their purpose from names or defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Generate an image using Replicate's Stable Diffusion model', which identifies the verb (generate), resource (image), and model. It distinguishes from siblings 'list-saved-images' and 'save-image'. However, it could be more precise by specifying 'from a text prompt'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, output handling, or when not to use it. The description assumes the agent already knows to use this for generation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list-saved-imagesA

List all saved images

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A3.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It only states 'List all saved images' but lacks details on pagination, ordering, or behavior when no images exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with one short sentence, front-loaded with the key action and resource. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and a simple output (likely an array of saved images), the description fully explains the tool's purpose without needing further elaboration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is 100%. The description implicitly means no arguments are needed, which is sufficient and adds no extra confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'List' and the resource 'all saved images'. It distinguishes this tool from its siblings 'generate-image' and 'save-image' by specifying a different action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus the sibling tools. It does not state any prerequisites or context for using this list operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

save-imageC

Save a generated image

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYes
image_urlYes
custom_filenameNoCustom filename for the saved image (without extension). If not provided, a UUID will be used.
target_directoryNoDirectory path where the image should be saved. If not provided, defaults to the MCP server's images directory.

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Save a generated image' without detailing side effects (e.g., whether it overwrites existing files, required permissions, or error handling). This is insufficient for an agent to understand the tool's behavior beyond a basic save operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it sacrifices informativeness. It could be restructured to include key details without being verbose. Every sentence should add value, and this one is too vague.

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?

Given the tool's complexity (4 parameters, no output schema, no annotations), the description is extremely incomplete. It does not explain return values, error conditions, or the result of saving. The agent cannot reliably invoke this tool based solely on this description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (custom_filename and target_directory have descriptions in schema, but required params prompt and image_url do not). The description adds no information about any parameter, failing to compensate for the missing schema descriptions. It does not explain what image_url or prompt mean for this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Save a generated image' clearly identifies the verb (save) and resource (generated image), and it distinguishes from sibling tools 'generate-image' (which creates but does not persist) and 'list-saved-images' (which lists existing saves). However, it could be more specific about the storage location or context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool vs alternatives. It does not state that this should be used after an image is generated, nor does it mention scenarios where this tool might be inappropriate. With siblings like generate-image and list-saved-images, explicit usage context is missing.

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. 3 tool updatesv1.0.1
    • First observedgenerate-image
    • First observedlist-saved-images
    • First observedsave-image
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: generating images, listing saved images, and saving images. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (generate-image, list-saved-images, save-image), making them predictable.

Tool Count4/5

3 tools is appropriate for a focused image generator server, covering the core workflow. Slightly minimal but not overly sparse.

Completeness4/5

Covers generation, listing, and saving. Missing a delete or update tool, but the core lifecycle is intact and agents can work without major gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches