Skip to main content
Glama
chrisurf

DALL-E 3 MCP Server

by chrisurf

DALL-E 3 MCP Server

CI/CD Pipeline npm version License Node.js Version

A Model Context Protocol (MCP) server that provides DALL-E 3 image generation capabilities. This server allows LLMs to generate high-quality images using OpenAI's DALL-E 3 model through the standardized MCP interface.

Features

  • 🎨 High-Quality Image Generation: Uses DALL-E 3 for state-of-the-art image creation

  • πŸ”§ Flexible Configuration: Support for different sizes, quality levels, and styles

  • πŸ“ Automatic File Management: Handles directory creation and file saving

  • πŸ›‘οΈ Robust Error Handling: Comprehensive error handling with detailed feedback

  • πŸ“Š Detailed Logging: Comprehensive logging for debugging and monitoring

  • πŸš€ TypeScript: Fully typed for better development experience

  • πŸ§ͺ Well Tested: Comprehensive test suite with high coverage

Related MCP server: OpenAI MCP

Installation

npx imagegen-mcp-d3

Using NPM

npm install -g imagegen-mcp-d3

From Source

git clone https://github.com/chrisurf/imagegen-mcp-d3.git
cd imagegen-mcp-d3
npm install
npm run build
npm start

Prerequisites

  • Node.js: Version 18.0.0 or higher

  • OpenAI API Key: You need a valid OpenAI API key with DALL-E 3 access

Configuration

Environment Variables

Set your OpenAI API key as an environment variable:

export OPENAI_API_KEY="your-openai-api-key-here"

Or create a .env file in your project root:

OPENAI_API_KEY=your-openai-api-key-here

Usage

With Claude Desktop

Add this server to your Claude Desktop configuration:

{
  "mcpServers": {
    "imagegen-mcp-d3": {
      "command": "npx",
      "args": ["imagegen-mcp-d3"],
      "env": {
        "OPENAI_API_KEY": "your-openai-api-key-here"
      }
    }
  }
}

With Other MCP Clients

The server implements the standard MCP protocol and can be used with any compatible client.

Available Tools

generate_image

Generates an image using DALL-E 3 and saves it to the specified location.

Parameters:

  • prompt (required): Text description of the image to generate

  • output_path (required): Full file path where the image should be saved

  • size (optional): Image dimensions - "1024x1024", "1024x1792", or "1792x1024" (default: "1024x1024")

  • quality (optional): Image quality - "standard" or "hd" (default: "hd")

  • style (optional): Image style - "vivid" or "natural" (default: "vivid")

Example:

{
  "name": "generate_image",
  "arguments": {
    "prompt": "A serene sunset over a mountain lake with pine trees",
    "output_path": "/Users/username/Pictures/sunset_lake.png",
    "size": "1024x1792",
    "quality": "hd",
    "style": "natural"
  }
}

Response:

The tool returns detailed information about the generated image, including:

  • Original and revised prompts

  • Image URL

  • File save location

  • Image specifications

  • File size

API Reference

Image Sizes

  • Square: 1024x1024 - Perfect for social media and general use

  • Portrait: 1024x1792 - Great for mobile wallpapers and vertical displays

  • Landscape: 1792x1024 - Ideal for desktop wallpapers and horizontal displays

Quality Options

  • Standard: Faster generation, good quality

  • HD: Higher quality with more detail (recommended)

Style Options

  • Vivid: More dramatic and artistic interpretations

  • Natural: More realistic and natural-looking results

Development

Setup

git clone https://github.com/chrisurf/imagegen-mcp-d3.git
cd imagegen-mcp-d3
npm install

Available Scripts

npm run dev          # Run in development mode with hot reload
npm run build        # Build for production
npm run start        # Start the built server
npm run test         # Run tests
npm run test:watch   # Run tests in watch mode
npm run test:coverage # Run tests with coverage report
npm run lint         # Run ESLint
npm run lint:fix     # Fix ESLint issues
npm run format       # Format code with Prettier
npm run typecheck    # Run TypeScript type checking

Project Structure

src/
β”œβ”€β”€ index.ts           # Main server implementation
β”œβ”€β”€ types.ts          # TypeScript type definitions
└── __tests__/        # Test files
    └── index.test.ts # Main test suite

Running Tests

# Run all tests
npm test

# Run tests with coverage
npm run test:coverage

# Run tests in watch mode during development
npm run test:watch

Error Handling

The server provides comprehensive error handling for common scenarios:

  • Missing API Key: Clear error message when OPENAI_API_KEY is not set

  • Invalid Parameters: Validation errors for required and optional parameters

  • API Errors: Detailed error messages from the OpenAI API

  • File System Errors: Handling of directory creation and file writing issues

  • Network Errors: Graceful handling of network connectivity issues

Logging

The server provides detailed logging for monitoring and debugging:

  • Request initiation and parameters

  • API communication status

  • Image generation progress

  • File saving confirmation

  • Error details and stack traces

Contributing

We welcome contributions! Please see our Contributing Guidelines for details.

Development Workflow

  1. Fork the repository

  2. Create a feature branch: git checkout -b feature/amazing-feature

  3. Make your changes

  4. Add tests for new functionality

  5. Ensure all tests pass: npm test

  6. Commit your changes: git commit -m 'Add amazing feature'

  7. Push to the branch: git push origin feature/amazing-feature

  8. Open a Pull Request

CI/CD

This project uses GitHub Actions for continuous integration and deployment:

  • Testing: Automated testing on multiple Node.js versions (18, 20, 22)

  • Code Quality: ESLint, Prettier, and TypeScript checks

  • Security: Dependency vulnerability scanning

  • Publishing: Automatic NPM publishing on release

  • Coverage: Local code coverage reporting

License

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

Support

Changelog

See CHANGELOG.md for a detailed history of changes.

Acknowledgments

  • OpenAI for the DALL-E 3 API

  • Anthropic for the Model Context Protocol specification

  • The MCP community for tools and documentation High-performance MCP for generating images using DALLΒ·E 3 – optimized for fast, scalable, and customizable inference workflows.

Available Tools

1 tool
generate_imageB

Generate an image using DALL-E 3

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYesText prompt for image generation
output_pathYesFull path where the image should be saved
sizeNoImage size1024x1024
qualityNoImage qualityhd
styleNoImage stylevivid

TDQS

B3.2/5.0
Behavior2/5

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

No annotations present, so description should disclose behavioral traits like API dependency, cost, rate limits, or side effects. Only states 'using DALL-E 3' without elaboration. Fails to inform agent of external service implications.

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?

Single concise sentence that is front-loaded and contains no unnecessary words. Every word earns its place.

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 no output schema and 5 parameters, the description fails to explain return behavior, error handling, or the effect of parameters like size/quality/style. Incomplete for a non-trivial generation tool.

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?

Input schema has 100% coverage with descriptions for all parameters. Description adds no additional parameter context beyond the schema, achieving baseline score.

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

Purpose5/5

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

Description clearly states it generates an image using DALL-E 3, with a specific verb and resource. No siblings exist, so differentiation is not needed.

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 on when to use this tool or alternatives. Since there are no siblings, lack of exclusion criteria is less critical, but still no usage context provided.

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 update
    • First observedgenerate_image

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of ambiguity; the tool's purpose is clear and distinct by default.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (generate_image), and with only one tool, naming consistency is trivially maintained.

Tool Count3/5

One tool feels thin for a server named 'DALL-E 3 MCP Server'. While the tool itself is non-trivial, the server would benefit from additional tools for variations or edits to be well-scoped.

Completeness3/5

The server only exposes image generation, missing other DALL-E 3 capabilities like editing or variations. This leaves notable gaps for agents expecting more comprehensive functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers