The mcp-4o-Image-Generator server enables AI-powered image generation and editing through the 4o-image API. You can:
Text-to-Image Generation: Create images from text descriptions.
Image Editing: Transform existing images based on text prompts.
Real-time Progress Updates: Receive feedback on generation status.
Browser Integration: Automatically open generated images in your default browser with clickable links provided.
Runs as a Node.js application, as indicated by the Node.js version compatibility badge.
Available as an npm package that can be installed and executed using npx.
Uses Shields.io for displaying version and compatibility badges in the README.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-4o-Image-Generator create a photo of a cat wearing sunglasses on a surfboard"
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.
An MCP server implementation that integrates with 4o-image API, enabling LLMs and other AI systems to generate and edit images through a standardized protocol. Create high-quality art, 3D characters, and custom images using simple text prompts.
Text-to-Image Generation: Create images from text descriptions with AI
Image Editing: Transform existing images using text prompts
Real-time Progress Updates: Get feedback on generation status
Browser Integration: Automatically open generated images in your default browser
Related MCP server: image-forge-mcp
generateImage
Generate images based on text prompts with optional image editing
Inputs:
prompt (string, required): Text description of the desired image
imageBase64 (string, optional): Base64-encoded image for editing or style transfer
Register for an account at 4o-image.app
Obtain your API key from the user dashboard
Set the API key as an environment variable when running the server
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"4o-image": {
"command": "npx",
"args": [
"-y",
"4oimage-mcp"
],
"env": {
"API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}Here's an example of using this MCP server with Claude:
Generate an image of a dog running on the beach at sunsetClaude will use the MCP server to generate the image, which will automatically open in your default browser. You'll also get a direct link to the image in Claude's response.
For image editing, you can include a base image and prompt Claude to modify it:
Edit this image to make the sky more dramatic with storm cloudsThis MCP server is licensed under the MIT License. You are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License.
Generate images using the 4o-image API and automatically open the results in your browser.
This tool generates images based on your prompt and automatically opens them in your default browser, while also returning a clickable link.
The tool supports two modes:
Text-to-image - Create new images using just a text prompt
Image editing - Provide a base image and prompt for editing or style transfer
The response will include a direct link to the generated image and detailed information.
Visit our website: https://4o-image.app/
| Name | Required | Description | Default |
|---|---|---|---|
| imageBase64 | No | Optional base image (Base64 encoded) for image editing or upscaling | |
| prompt | Yes | Text description of the desired image content |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context beyond the input schema by describing automatic browser opening, return of a clickable link, and support for two modes. However, it does not cover important behavioral traits such as rate limits, authentication needs, error handling, or response format details, leaving gaps for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and front-loaded, starting with the core functionality and then detailing modes and responses. Most sentences add value, but the final promotional sentence ('Visit our website...') is extraneous and does not aid tool selection or invocation, slightly reducing efficiency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (image generation with two modes), no annotations, and no output schema, the description is moderately complete. It covers purpose, usage modes, and some behavioral aspects (browser opening, link return), but lacks details on output structure, error cases, or operational constraints, which are important for a tool without structured output documentation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents both parameters (imageBase64 and prompt) adequately. The description adds marginal value by explaining the two modes that correspond to these parameters, but it does not provide additional syntax, format, or constraint details beyond what the schema states. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Generate images using the 4o-image API' and specifies it 'automatically opens the results in your browser.' It distinguishes between text-to-image and image editing modes, providing specific functionality details. However, without sibling tools, differentiation from alternatives is not applicable, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context by outlining two modes (text-to-image and image editing) and indicating when to use each based on whether an imageBase64 parameter is provided. It mentions that the tool opens results in the browser and returns a clickable link, offering practical guidance. However, it lacks explicit exclusions or comparisons to alternatives, as no sibling tools exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0generateImageWith only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generateImage' has a clear, distinct purpose for image generation and editing.
The tool name 'generateImage' follows a consistent verb_noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is clear and appropriate for its function.
A single tool is too few for the server's purpose of image generation and editing, as it lacks coverage for related operations like listing generated images, managing settings, or handling errors. This minimal set limits agent functionality and feels incomplete for the domain.
The tool surface is severely incomplete for an image generation server. While 'generateImage' covers creation and editing, there are obvious gaps such as no tools for retrieving past images, deleting images, or configuring generation parameters, which are essential for a full workflow.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for Qwen Image 3 AI image generation
Generate AI images and videos from any compatible MCP client.
Generate game-ready 3D models, textures, and audio from natural language, over MCP.
MCP server for Hailuo (MiniMax) AI video generation
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Antipas/4oimage-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server