Skip to main content
Glama
deenesjakoruzh
Sunwood-ai-labs

Ideogram MCP Server

by Sunwood-ai-labs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

📦 Project Overview

  • A TypeScript tool that allows you to use Ideogram API (v3.0) via MCP server

  • Multi-function including image generation, style reference, magic prompt, aspect ratio, model selection, etc.

  • Can be used immediately with Claude Desktop and other MCP clients

Related MCP server: OpenAI MCP

⚡️ Quick Start

If you want to connect to Claude Desktop or other MCP clients at lightning speed,
Just copy and paste the JSON snippet below into your configuration file!

{
  "mcpServers": {
    "ideogram": {
      "command": "npx",
      "args": [
        "@sunwood-ai-labs/ideagram-mcp-server"
      ],
      "env": {
        "IDEOGRAM_API_KEY": "your_api_key_here"
      }
    }
  }
}

🛠️ MCP Tool Specifications

generate_image

Parameter list (latest version)

Parameters

Type

explanation

Required/Optional

remarks

prompt

string

Image generation prompt (English recommended)

Required

aspect_ratio

string

Aspect ratio (e.g. "1x1", "16x9", "4x3", etc.)

any

15 types

resolution

string

Resolution (see official documentation, 69 types in total)

any

seed

integer

Random number seed (to ensure reproducibility)

any

0 to 2147483647

magic_prompt

string

Magic prompt ("AUTO"

"ON"

"OFF"

rendering_speed

string

Rendering speed for v3 ("TURBO"

"DEFAULT"

"QUALITY"

style_codes

string[]

8-character style code sequence

any

style_type

string

Style type ("AUTO"

"GENERAL"

"REALISTIC"

negative_prompt

string

Exclusions (English recommended)

any

num_images

number

Number of generated images (1 to 8)

any

style_reference

object

Style Reference (New in Ideogram 3.0)

any

Details below

└ urls

string[]

Reference image URL array (up to 3)

any

└ style_code

string

Style Code

any

└ random_style

boolean

Use random style

any

output_dir

string

Image storage directory (default: "docs")

any

base_filename

string

Base for saved filename (default: "ideogram-image")

any

Timestamp and ID assignment

blur_mask

boolean

Blur the edges of the image (set to true for mask compositing)

any

Default: false

📝 Usage example

const result = await use_mcp_tool({
  server_name: "ideagram-mcp-server",
  tool_name: "generate_image",
  arguments: {
    prompt: "A beautiful sunset over mountains",
    aspect_ratio: "16x9",
    rendering_speed: "QUALITY",
    num_images: 2,
    style_reference: {
      urls: [
        "https://example.com/ref1.jpg",
        "https://example.com/ref2.jpg"
      ],
      random_style: false
    },
    blur_mask: true
  }
});

🧑‍💻 Develop, build, and test

  • npm run build ... TypeScript build

  • npm run watch ... development mode (automatic build)

  • npm run lint ... Code linting

  • npm test ... run tests

🗂️ Directory structure

ideagram-mcp-server/
├── assets/
├── docs/
│   └── ideogram-image_2025-05-18T06-31-45-777Z.png
├── src/
│   ├── tools/
│   ├── types/
│   ├── utils/
│   ├── ideogram-client.ts
│   ├── index.ts
│   ├── server.ts
│   └── test.ts
├── .env.example
├── package.json
├── tsconfig.json
├── README.md
└── ...（省略）

📝 Contributions

  1. Fork this repository

  2. Create a new branch ( git checkout -b feature/awesome )

  3. Commit changes (Commit messages should be in Japanese and emojis are recommended!)

  4. Push and pull request creation

🚀 Deploy & Release

  • Automatic npm publishing with GitHub Actions

  • Version update → Automatic deployment by pushing tags

npm version patch|minor|major
git push --follow-tags

For details, see docs/npm-deploy.md !

📄 License

MIT

Available Tools

1 tool
generate_imageC

Generate an image using Ideogram AI

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt to use for generating the image (must be in English)
aspect_ratioNoThe aspect ratio for the generated image (see official docs for all 15 values)
resolutionNoThe resolution for the generated image (see official docs for all 69 values)
seedNoRandom seed. Set for reproducible generation.
magic_promptNoWhether to use magic prompt
rendering_speedNoRendering speed for v3 (TURBO/DEFAULT/QUALITY)
style_codesNoArray of 8-char style codes
style_typeNoThe style type for generation
style_reference_imagesNoA set of images to use as style references (max 10MB, JPEG/PNG/WebP)
negative_promptNoDescription of what to exclude from the image (must be in English)
num_imagesNoNumber of images to generate (1-8)
style_referenceNoStyle reference options for Ideogram 3.0
output_dirNoDirectory to save generated images (default: 'docs').
base_filenameNoBase filename for saved images (default: 'ideogram-image'). Timestamp and image ID will be appended automatically.
blur_maskNoApply a blurred mask to the image edges (using a fixed mask image). If true, the output image will have blurred/feathered edges. (default: false)

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states the basic action without mentioning rate limits, authentication needs, output format, error conditions, or cost implications. For a complex image generation tool with 15 parameters, this leaves significant behavioral gaps.

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 a single, efficient sentence that states the core purpose without unnecessary elaboration. It's appropriately sized for a tool name that clearly indicates its function, and there's no wasted verbiage or structural issues.

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 the tool's complexity (15 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain what the tool returns, error handling, performance characteristics, or typical use patterns. For an image generation tool with many configuration options, more context is needed to help the agent use it effectively.

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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose3/5

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

The description 'Generate an image using Ideogram AI' states the basic action (generate) and resource (image) but lacks specificity. It doesn't mention what kind of images, quality levels, or typical use cases. Without sibling tools, differentiation isn't needed, but the purpose remains vague beyond the basic verb-noun pairing.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, ideal scenarios, or limitations. Without sibling tools, there's no need for differentiation, but the absence of any usage context leaves the agent with no guidance on appropriate application.

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

C2.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'generate_image' has a clearly distinct and unambiguous purpose.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'generate_image' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server named 'Ideogram MCP Server', which suggests a broader scope for image generation or AI tasks. A single tool feels thin and limited for such a domain.

Completeness2/5

The tool surface is severely incomplete for an image generation server. It only offers generation with no options for editing, listing, deleting, or managing images, creating 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/Sunwood-ai-labs/ideagram-mcp-server'

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