Watercolor MCP Server

Connect an MCP-compatible agent to the stateless watercolor generation tools.

Endpoint

Connect with Streamable HTTP at https://www.aiwatercolorgenerator.com/api/mcp. Send the same API key used by the REST API as Authorization: Bearer <API_KEY>.

Client configuration

MCP clients use different configuration file names, but the connection values are:

{
  "name": "ai-watercolor-generator",
  "transport": "streamable-http",
  "url": "https://www.aiwatercolorgenerator.com/api/mcp",
  "headers": {
    "Authorization": "Bearer ${AIWATERCOLOR_API_KEY}"
  }
}

Store the key in an environment variable or secret manager. Do not commit a real key.

Tools

Tool	Purpose
`generate_watercolor`	Submit an asynchronous text-to-watercolor task
`edit_watercolor`	Submit an asynchronous edit using uploaded input images
`get_watercolor_task`	Read task status, outputs, or failure details

`generate_watercolor`

Required: prompt. Optional: model, aspect_ratio, resolution, and idempotency_key.

`edit_watercolor`

Required: prompt and input_images (1–9 trusted application-storage URLs). Optional: model, aspect_ratio, resolution, and idempotency_key.

`get_watercolor_task`

Required: task_id. Pass the returned id from a generation or edit tool call as task_id.

Generation and edit tools return a task identifier rather than waiting for image completion. Call get_watercolor_task until the task reaches succeeded, failed, or canceled.

Behavior

The MCP server is stateless. It does not create chats, retain conversation history, run the website agent, or reveal internal prompts. Calls use the same credits, ownership rules, concurrency limit, and rate limits as the REST API.

For raw HTTP requests and complete schemas, see the REST API documentation and OpenAPI document.