Skip to main content
Glama
enesjakozh
sanxfxteam

Gemini MCP Image Generation Server

by sanxfxteam
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Gemini Image Generation MCP Server

This is a Model Context Protocol (MCP) server that provides image generation capabilities using Google's Gemini 2 API.

Quick Start

  1. Get Gemini API Key

  2. Configure Claude Desktop

    • Locate your config file:

      Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

    • Add Gemini configuration:

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

  3. Restart Claude Desktop

Related MCP server: Image Toolkit MCP Server

Setup

  1. Install dependencies:

npm install

  1. Set up your environment variables: Create a .env file in the root directory and add your Google API key:

GEMINI_API_KEY=your_api_key_here

Usage

Run the server:

npm start

To test

npx @modelcontextprotocol/inspector npm run start

Available Tools

generateImage

Generates images using Gemini 2's experimental image generation API.

Parameters:

  • prompt (string, required): The description of the image you want to generate

  • numSamples (number, optional, default: 4): Number of images to generate

  • aspectRatio (string, optional, default: '1:1'): Aspect ratio of the generated images

  • personGeneration (string, optional, default: 'ALLOW_ADULT'): Person generation settings

Example MCP request:

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

Notes

  • This server uses the experimental image generation feature of Gemini 2

  • Make sure you have appropriate access and API keys from Google

  • The server communicates using the Model Context Protocol over 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.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0
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

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/sanxfxteam/gemini-mcp-server'

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