Skip to main content
Glama
enesjakozh
GMKR

mcp-image-generator

by GMKR
OverviewSchemaSourceRelated ServersScoreDiscussions
TypeScript
Hybrid

MCP画像ジェネレータ

Together AIの画像生成モデルを用いて画像を生成するためのモデルコンテキストプロトコル（MCP）サーバーです。このMCPサーバーは、ローカルまたはSSEエンドポイントを使用して実行できます。MCP画像ジェネレーターにはプロバイダーが必要ですが、現在は「Replicate」と「Together」のみがサポートされています。環境変数TOGETHER_API_KEYまたはREPLICATE_API_TOKENを設定し、 PROVIDER環境変数を「replicate」または「together」に設定する必要があります。

SSEエンドポイント（Docker環境）

リポジトリをクローンする

git clone https://github.com/gmkr/mcp-imagegen.git
cd mcp-imagegen

Dockerコンテナの構築と実行

docker build -f Dockerfile.server -t mcp-imagegen .
docker run -p 3000:3000 mcp-imagegen

MCPクライアントでの設定

{
  "mcpServers": {
    "imagegenerator": {
      "url": "http://localhost:3000/sse",
      "env": {
        "PROVIDER": "replicate",
        "REPLICATE_API_TOKEN": "your-replicate-api-token"
      }
    }
  }
}

使用する MCP サーバーのエンドポイントへのurlを調整します。 provider 「replicate」または「together」にすることができます。

Related MCP server: pixel-surgeon-mcp

stdioを使用してローカルで実行する

前提条件

  • Node.js

  • Together AI APIキーまたはレプリケートAPIトークン

インストール

  1. リポジトリをクローンします。

    git clone https://github.com/gmkr/mcp-imagegen.git
cd mcp-imagegen

  2. 依存関係をインストールします:

    pnpm install

構成

MCPクライアント用の設定ファイルを作成します。設定例を以下に示します。

{
  "mcpServers": {
    "imagegenerator": {
      "command": "pnpx",
      "args": [
        "-y",
        "tsx",
        "/path/to/mcp-imagegen/src/index.ts"
      ],
      "env": {
        "PROVIDER": "replicate",
        "REPLICATE_API_TOKEN": "your-replicate-api-token"
      }
    }
  }
}

/path/to/mcp-imagegenクローンしたリポジトリへの絶対パスに置き換え、 your-replicate-api-tokenを実際の Replicate API トークンに置き換えます。

使用法

MCP イメージ ジェネレーターには、テキスト プロンプトに基づいてイメージを生成するために使用できるgenerate_imageというツールが用意されています。

ツール: generate_image

提供されたプロンプトに基づいて画像を生成します。

パラメータ:

  • prompt (文字列): 画像を生成するためのテキストプロンプト

  • width （数値、オプション）：生成する画像の幅（デフォルト：512）

  • height （数値、オプション）：生成する画像の高さ（デフォルト：512）

  • numberOfImages (数値、オプション): 生成する画像の数 (デフォルト: 1)

環境変数

  • PROVIDER : 画像生成に使用するプロバイダー (デフォルト: "replicate")

  • REPLICATE_API_TOKEN : Replicate APIトークン

  • TOGETHER_API_KEY : Together AI APIキー

  • MODEL_NAME : 画像生成に使用するモデル（デフォルト: "black-forest-labs/flux-schnell"）

ライセンス

マサチューセッツ工科大学

Available Tools

1 tool
generate_imageA

Generates and returns an image based on the provided promptUse this tool when you need to generate an image based on a promptThe image will be returned as a base64 encoded string

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt to generate an image for
widthNoThe width of the image to generate
heightNoThe height of the image to generate
numberOfImagesNoThe number of images to generate

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the image is 'returned as a base64 encoded string,' which adds useful behavioral context beyond the input schema. However, it lacks details on potential limitations (e.g., rate limits, quality constraints, or error conditions), leaving gaps for a mutation tool.

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 front-loaded with the purpose and usage guidelines in two sentences, with no wasted words. However, the lack of punctuation between sentences ('promptUse this tool') slightly reduces readability, preventing a perfect score of 5.

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

Completeness3/5

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

Given the tool's complexity (image generation with 4 parameters) and no annotations or output schema, the description is moderately complete. It covers the basic operation and output format but lacks details on behavioral traits (e.g., performance, errors) and does not explain return values beyond the base64 string, leaving room for improvement.

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

Parameters3/5

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

The schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description does not add any parameter-specific details beyond what the schema provides (e.g., format or constraints for 'prompt' or 'width'). Thus, it meets the baseline of 3 but does not enhance parameter understanding.

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 the tool's purpose: 'Generates and returns an image based on the provided prompt.' It specifies both the action (generate and return) and the resource (image). However, with no sibling tools provided, it cannot demonstrate differentiation from alternatives, which prevents a score of 5.

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

Usage Guidelines4/5

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

The description includes explicit guidance: 'Use this tool when you need to generate an image based on a prompt.' This clearly indicates the primary use case. However, it lacks exclusions or alternatives (e.g., when not to use it or other tools for similar tasks), which prevents a score of 5.

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. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedgenerate_image
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_image' has a clear and distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The single tool name 'generate_image' follows a clear verb_noun pattern. Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate.

Tool Count2/5

A single tool is too few for a server named 'mcp-image-generator', which suggests a broader scope for image generation tasks. While the tool covers basic generation, the count feels thin and lacks operations like editing, upscaling, or managing generated images that might be expected.

Completeness2/5

The tool set is severely incomplete for an image generation domain. It only provides generation, with no coverage for common operations like editing images, adjusting parameters, retrieving generation history, or handling different formats, which will limit agent capabilities and cause workarounds.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GMKR/mcp-imagegen'

If you have feedback or need assistance with the MCP directory API, please join our Discord server