Skip to main content
Glama
enesjakozh
sanxfxteam

Gemini MCP Image Generation Server

by sanxfxteam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

제미니 이미지 생성 MCP 서버

이는 Google의 Gemini 2 API를 사용하여 이미지 생성 기능을 제공하는 MCP(Model Context Protocol) 서버입니다.

빠른 시작

  1. Gemini API 키 받기

  2. Claude Desktop 구성

    • 구성 파일을 찾으세요.

      지엑스피1

    • Gemini 구성 추가:

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

  3. Claude Desktop을 다시 시작하세요

Related MCP server: Image Toolkit MCP Server

설정

  1. 종속성 설치:

npm install

  1. 환경 변수를 설정하세요. 루트 디렉토리에 .env 파일을 만들고 Google API 키를 추가하세요.

GEMINI_API_KEY=your_api_key_here

용법

서버를 실행합니다:

npm start

테스트하려면

npx @modelcontextprotocol/inspector npm run start

사용 가능한 도구

이미지 생성

Gemini 2의 실험적 이미지 생성 API를 사용하여 이미지를 생성합니다.

매개변수:

  • prompt (문자열, 필수): 생성하려는 이미지에 대한 설명

  • numSamples (숫자, 선택 사항, 기본값: 4): 생성할 이미지 수

  • aspectRatio (문자열, 선택 사항, 기본값: '1:1'): 생성된 이미지의 종횡비

  • personGeneration (문자열, 선택 사항, 기본값: 'ALLOW_ADULT'): 개인 생성 설정

MCP 요청 예시:

{
  "tool": "generateImage",
  "params": {
    "prompt": "A serene mountain landscape at sunset",
    "numSamples": 2,
    "aspectRatio": "16:9"
  }
}

노트

  • 이 서버는 Gemini 2의 실험적 이미지 생성 기능을 사용합니다.

  • Google에서 적절한 액세스 키와 API 키가 있는지 확인하세요.

  • 서버는 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
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

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

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches