A
licenseA
qualityD
maintenanceAn MCP server that turns Claude into a full image production studio, enabling creation, editing, resizing, and brand-consistent asset generation across multiple platforms.
6
MIT
MCP Asset Generator
by jbrower95
mcp-asset-gen
このツールを使うと、ClaudeはOpenAIと通信し、 gpt-image-1を使って画像アセットを生成できます。これは、ゲームやWeb開発で個々のアセットを印刷する必要がある場合に非常に便利です。
要件
ノード
OpenAI APIキー
現時点では、これには ID 検証を伴う組織が必要であることに注意してください。
インストール
OpenAI Web サイトから API KEY を取得します。
シェルで API_KEY としてエクスポートします。
export API_KEY=sk-proj-....次に、これを同じシェルに貼り付けます。
jq --arg apiKey "$API_KEY" \
'.mcpServers = (.mcpServers // {}) |
.mcpServers["mcp-asset-gen"] = {
type: "stdio",
command: "npx",
args: ["mcp-asset-gen"],
env: { API_KEY: $apiKey }
}' ~/.claude.json > ~/.claude.tmp && mv ~/.claude.tmp ~/.claude.json完了です！クロードに画像生成を依頼すると、
> generate a small logo image that i could use for my arcade game
I'll generate a logo for your arcade game. Please provide a more specific description of what you'd like to see in the logo (colors, style,
game theme, etc.) for better results.
> It should look like an old school pacman machine (liek a wooden arcade machine)
⏺ mcp-asset-gen:generateImag(outputPathAbsolute: "/Users/jbrower/projects/mcp-asset-gen/arcade-logo.png", prompt: "An old school wooden arcade…
(MCP) machine logo in the style of Pacman, with retro colors and pixelated elements, top-down view of the cabinet,
nostalgic arcade gaming feel, vibrant colors against dark background", quality: "high", size: "1024x1024")
⎿ The image is now available at /Users/jbrower/projects/mcp-asset-gen/arcade-logo.png.
⏺ Generated arcade logo saved to /Users/jbrower/projects/mcp-asset-gen/arcade-logo.pngAvailable Tools
1 toolgenerateImageD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| outputPathAbsolute | Yes | The absolute path where the image should be written out. | |
| prompt | Yes | Text description of the desired image content | |
| quality | No | The quality of the image. | |
| size | No | Size of the generated image |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
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 tool update
v1.0.0- First observed
generateImage
TDQS
D1.7/5.0
Scored across 1 tool
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness1/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
MCP server for Qwen Image 3 AI image generation
MCP server for OpenAI Sora AI video generation
MCP server for NanoBanana AI image generation and editing
MCP server for Grok Imagine AI video generation
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to generate images using Google's Gemini image generation models.MIT
- AlicenseAqualityCmaintenanceAn MCP server that generates and edits images using OpenAI's GPT Image model, allowing users to create images from text descriptions and edit existing images through natural language.115 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that enables Claude to generate images using the OpenAI API.7 npmMIT