ChongPlus Image MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| setup_statusA | Check whether this computer has a saved ChongPlus API key. Call this before image generation when setup is uncertain. |
| configure_api_keyB | Save a user's ChongPlus API key locally. api_key is sensitive: never repeat it in chat, logs, or tool results. |
| list_image_optionsA | List ChongPlus image generation limits. Use this to choose a supported image size or count. |
| generate_imageB | Generate one to four images from a prompt and save them locally. Returns absolute image paths. |
| edit_imageB | Edit one existing local image with a prompt and save the result locally. image_path must be a local file path, not a URL. |
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 5 tools
Each tool has a clearly distinct purpose: checking setup, configuring API key, listing options, generating images, and editing images. No overlap exists.
Tool names follow a consistent verb_noun pattern (setup_status, configure_api_key, etc.) with underscores, making them predictable and easy to understand.
With 5 tools, the server is well-scoped for image generation, covering setup, configuration, option discovery, generation, and editing without being too sparse or bloated.
The tool surface covers the core workflow (setup, config, generate, edit). A minor gap is the absence of a tool to list or manage previously generated images, but this does not severely impact the primary use case.