MCP Asset Generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | OpenAI API Key required for accessing the image generation service |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generateImageD | – |
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 confusion between tools. The tool's purpose is clearly implied by its name even without a description.
Single tool uses a clear camelCase convention, and there are no other tools to introduce inconsistencies. The name is readable and follows a logical pattern.
A single tool feels too few for a server called 'Asset Generator,' which implies a broader suite of asset-creation capabilities. This is under-scoped and likely limits practical use.
With only generateImage and no other operations, the server covers a tiny slice of asset generation. There is no way to handle other asset types or perform related tasks, making the surface severely incomplete for the stated domain.