How do I use Ideogram MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Ideogram MCP Server Generate a realistic portrait of a cat wearing a hat" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Ideogram MCP Server

by flowluap

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Ideogram MCP Server

License: MIT Node.js Version npm version

A Model Context Protocol (MCP) server implementation for the Ideogram AI API. This server provides tools for generating, editing, and describing images using Ideogram's powerful AI models.

Features

Generate images from text descriptions
Edit existing images using masks
Generate descriptions for images
Download generated images to local directory
Prompt templates for common operations

Related MCP server: Replicate Ideogram V3 MCP Server

Installation

Clone the repository

git clone https://github.com/flowluap/ideogram-mcp-server.git
cd ideogram-mcp-server

Install dependencies

npm install

Build the project

npm run build

Cursor Integration

To use this MCP in Cursor, add the following configuration to your Cursor settings (Settings > AI > Model Context Protocol):

{
  "mcps": {
    "ideogram-mcp": {
      "command": "node",
      "args": ["PATH_TO_YOUR_DIST/index.js"],
      "env": {
        "IDEOGRAM_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace:

PATH_TO_YOUR_DIST/index.js with the absolute path to your built index.js file
your-api-key-here with your actual Ideogram API key

Example (redacted):

{
  "mcps": {
    "ideogram-mcp": {
      "command": "node",
      "args": ["/path/to/ideogram-mcp-server/dist/index.js"],
      "env": {
        "IDEOGRAM_API_KEY": "xxxxx-REDACTED-xxxxx"
      }
    }
  }
}

Available Tools

generate
- Generate images from text prompts
- Parameters:
  - prompt: string (required)
  - aspect_ratio: string (optional) - One of: ASPECT_1_1, ASPECT_16_9, ASPECT_9_16, ASPECT_4_3, ASPECT_3_4
  - model: string (optional) - One of: V_1, V_2, V_2_TURBO
  - magic_prompt_option: string (optional) - One of: AUTO, ON, OFF
  - num_images: number (optional) - Between 1 and 8
  - seed: number (optional) - Between 0 and 2147483647
edit
- Edit images using masks
- Parameters:
  - image_file: string (required) - Base64 or file path
  - mask: string (required) - Base64 or file path
  - prompt: string (required)
  - model: string (required) - One of: V_2, V_2_TURBO
describe
- Generate descriptions for images
- Parameters:
  - image_file: string (required) - Base64 or file path
download_images
- Download generated images to local directory
- Parameters:
  - urls: string[] (required) - Array of image URLs
  - output_dir: string (required) - Output directory path

Prompt Templates

generate_image
- Template for generating images
- Parameters:
  - description: string

Development

# Build the project
npm run build

# Run in development mode
npm run dev

# Run tests
npm test

# Run linter
npm run lint

Requirements

Node.js >= 18.0.0
Ideogram API key

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

Fork the repository
Create your feature branch
Commit your changes
Push to the branch
Create a new Pull Request

Available Tools

4 tools

describeD

ParametersJSON Schema

Name	Required	Description	Default
`image_file`	Yes

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.

download_imagesD

ParametersJSON Schema

Name	Required	Description	Default
`urls`	Yes
`output_dir`	Yes

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.

editD

ParametersJSON Schema

Name	Required	Description	Default
`image_file`	Yes
`mask`	Yes
`prompt`	Yes
`model`	Yes

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.

generateD

ParametersJSON Schema

Name	Required	Description	Default
`prompt`	Yes
`aspect_ratio`	No
`model`	No
`magic_prompt_option`	No
`num_images`	No
`seed`	No

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

4 tool updatesv1.0.0Jun 10, 2026
- First observeddescribe
- First observeddownload_images
- First observededit
- First observedgenerate

Install Server

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

TDQS

D1.5/5.0

Disambiguation2/5

Tool names are distinct (describe, download_images, edit, generate) but without descriptions, an agent cannot reliably determine their boundaries. For example, 'describe' might overlap with 'generate' if generating a description, leading to potential misselection.

Naming Consistency2/5

Naming is inconsistent: 'describe', 'edit', and 'generate' are single verbs, while 'download_images' uses a verb_noun pattern with an underscore. No consistent verb_noun or camelCase pattern is followed.

Tool Count3/5

4 tools is within the typical well-scoped range (3-15), but for an image generation server, the set feels slightly thin. Still, each tool appears to serve a distinct purpose without being excessive.

Completeness3/5

The tools cover basic operations: generate, edit, describe, and download images. However, obvious gaps exist, such as missing list, delete, or style-transfer tools, which may cause agent failures in common workflows.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

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

Related MCP Connectors

fengyinxia-jimeng-mcp
ai.smithery
Create images and videos from prompts, with options for image mixing, reference images, and start/…
Image & Video Processing Multimedia Processing
2
APICK AI A
app.apick
LLM chat, text tools, image generation, editing and batch image jobs
911
AI Media StudioOAuth
ai.b77
Generate images, videos, voiceovers, and captions from a chat prompt.
AI & Machine Learning Image & Video Processing Audio Processing
1
Avocado AI
io.github.Wandersonjack
Generate AI images, videos, music, SFX & speech in any AI assistant. Results appear inline in chat.
AI & Machine Learning Image & Video Processing Marketing
2

Related MCP Servers

fal-ai Ideogram V3 MCP Server
Image & Video Processing Multimedia Processing
PierrunoYT
A
license
Not graded
quality
Not graded
maintenance
Enables high-quality AI image generation with superior text rendering using the fal-ai/ideogram/v3 model. Supports advanced style control, custom dimensions, color palettes, reference images, and queue-based generation with automatic local image downloads.
Updated a year ago (2025-09-15 20:06 UTC)
-
Replicate Ideogram V3 MCP
Image & Video Processing Multimedia Processing
PierrunoYT
A
license
B
quality
Not graded
maintenance
Enables AI-powered image generation using the Ideogram V3 Balanced model via Replicate. Supports text-to-image generation, inpainting, style transfer with 60+ presets, custom resolutions, and reproducible outputs with local image storage.
Updated a year ago (2025-09-15 20:17 UTC)
2
-
Gemini Image MCP Server
Image & Video Processing AI & Machine Learning
Pritish053
A
license
A
quality
D
maintenance
Provides image generation, modification, and analysis capabilities using Google's Gemini API, enabling AI-powered image operations through natural language.
Updated 5 months ago (2026-04-14 12:44 UTC)
5
23
MIT
ideogram-mcp-server
AI & Machine Learning Image & Video Processing
takeshijuan
A
license
Not graded
quality
C
maintenance
Enables LLM applications to generate, edit, describe, upscale, remix, reframe, and replace backgrounds in images using the Ideogram AI API.
Updated 5 months ago (2026-03-31 07:06 UTC)
20
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/flowluap/ideogram-mcp-server'

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