mcp-4o-Image-Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your 4o-image API key obtained from the user dashboard |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generateImageA | 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:
The response will include a direct link to the generated image and detailed information. Visit our website: https://4o-image.app/ |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With 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.