Skip to main content
Glama
clawdbotworker

imagegen-mcp-x402

by clawdbotworker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imagegen-mcp

MCP server for AI image generation, powered by imagegen.coinopai.com. Payments are handled automatically via x402 micropayments on Base mainnet — no API keys, no subscriptions, just a funded wallet.

Cost: $0.10 USDC per image (Base mainnet)

What it does

Exposes a single generate_image tool that any MCP-compatible client (Claude Desktop, Cursor, Windsurf, etc.) can call. When invoked, the server automatically pays the $0.10 USDC gate and returns a PNG image URL.

Requirements

  • Node.js 18+

  • A Base wallet private key funded with USDC

Claude Desktop config

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "imagegen": {
      "command": "npx",
      "args": ["-y", "coinopai-imagegen"],
      "env": {
        "WALLET_PRIVATE_KEY": "0x<your-base-wallet-private-key>"
      }
    }
  }
}

npx usage

WALLET_PRIVATE_KEY=0x<your-key> npx coinopai-imagegen

Tool reference

generate_image

Generate an AI image from a text prompt.

Inputs:

Parameter

Type

Required

Description

prompt

string

Yes

Natural language image description

aspect

string

No

1:1 (default), 16:9, 9:16, 4:3

Output:

{
  "image_url": "https://...",
  "prompt": "your prompt",
  "aspect": "1:1",
  "generated_at": "2026-05-13T00:00:00.000Z"
}

Example prompts:

  • "a cyberpunk wolf in neon rain"

  • "a peaceful mountain lake at sunrise, photorealistic"

  • "abstract geometric art, vibrant colors, 4K"

Cost disclosure

Each generate_image call costs $0.10 USDC deducted from your WALLET_PRIVATE_KEY wallet on Base mainnet. Use a purpose-built low-balance wallet, not your primary wallet.

$1 USDC ≈ 10 images.

Smithery

Available on Smithery — search for imagegen-mcp.

License

MIT

Available Tools

1 tool
generate_imageA

Generate an AI image from a text prompt. Costs $0.10 USDC per image, paid automatically via x402 on Base mainnet. Returns a PNG image URL.

ParametersJSON Schema
NameRequiredDescriptionDefault
promptYesNatural language description of the image to generate
aspectNoAspect ratio: 1:1 (default, 1024x1024), 16:9 (1024x576), 9:16 (576x1024), 4:3 (1024x768)

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses cost ($0.10), payment method (x402 on Base), and return type (PNG URL). This is substantial behavioral context.

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?

Three sentences, all essential. Purpose is front-loaded, followed by cost and return. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers input (via schema), cost, payment, and output format. For a simple generation tool with no output schema, this is fairly complete. Minor omissions like generation time or content policies are acceptable.

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?

Schema coverage is 100%, so baseline is 3. Description adds no extra parameter meaning beyond the schema, which is acceptable.

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?

The description clearly states 'Generate an AI image from a text prompt', using a specific verb and resource. It also includes cost and return type, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use (cost and payment method), but no explicit when-not-to-use or alternatives. Since no sibling tools exist, differentiation is less critical.

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 updatev1.0.0
    • First observedgenerate_image
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined.

Naming Consistency5/5

A single tool name cannot be inconsistent. It follows a clear verb_noun pattern ('generate_image'), which is appropriate.

Tool Count4/5

The server focuses solely on image generation from text prompts, which can reasonably be handled by a single tool. However, the inclusion of payment handling (x402) suggests potential missing tools for balance or transaction management.

Completeness3/5

The server provides only the core image generation functionality. Missing features like image history, deletion, or payment status tools may limit agent capabilities, but the basic use case is covered.

Resources

Related MCP Connectors

Related MCP Servers