AI Watercolor Generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIWATERCOLOR_API_KEY | Yes | Your AI Watercolor Generator API key. Required to authenticate with the hosted API. |
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 |
|---|---|
| generate_watercolorB | Create watercolor artwork from a text prompt as an asynchronous task. |
| upload_watercolor_inputB | Upload a local JPEG, PNG, or WebP file for watercolor editing. |
| edit_watercolorB | Transform uploaded images into watercolor artwork as an asynchronous task. |
| get_watercolor_taskC | Get the current status, output, or error for a watercolor task. |
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 4 tools
Each tool has a clearly distinct role: text-to-watercolor generation, input image upload, image-to-watercolor editing, and task status retrieval. There is no overlap or ambiguity between the tools.
All tool names follow a consistent verb_noun snake_case pattern: generate_, upload_, edit_, get_. The domain term 'watercolor' appears in every name, reinforcing a clear and predictable convention.
With only 4 tools, the server is tightly scoped to its purpose. Each tool is necessary for the core workflow of generating or editing watercolor art asynchronously, and none are redundant.
The tool set covers the full lifecycle for both generation paths: create via prompt, upload source, edit, and check status. Minor gaps such as canceling a task or listing all tasks prevent a perfect score, but the core workflows are not blocked.