pdhapi-image-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDHAPI_MODEL | No | Default model for image generation. | gpt-image-2.5-flare |
| PDHAPI_API_KEY | No | PdhAPI Key | |
| PDHAPI_BASE_URL | No | Base URL of the PdhAPI, may end with /v1. | https://pdhlzy.com |
| PDHAPI_SAVE_DIR | No | Directory where output images are saved. | ~/Pictures/pdhapi-out |
| PDHAPI_EDIT_MODEL | No | Default model for image editing. | gpt-image-2.5-sunburst |
| PDHAPI_INPUT_ROOT | No | Optional root directory for reference images. If not set, user-provided local image paths can be read. | |
| PDHAPI_API_KEY_FILE | No | Path to a local UTF-8 file containing only the PdhAPI Key (lower priority than PDHAPI_API_KEY). | |
| PDHAPI_DOWNLOAD_HOSTS | No | Comma-separated list of additional exact domains allowed for downloading images. Default is only the interface host. | |
| PDHAPI_TIMEOUT_SECONDS | No | Timeout for each API call in seconds. Default 300, valid range 1–900. | 300 |
| PDHAPI_API_KEY_KEYCHAIN | No | Set to 'true' to read the PdhAPI Key from the system credential manager (macOS Keychain / Windows Credential Manager / Linux Secret Service). | false |
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 |
|---|---|
| server_infoA | Read PdhAPI configuration without revealing keys or contacting the provider. |
| image_generateB | Generate images using PdhAPI. This uses paid API quota. Returns local files and image previews. Do not retry automatically after a timeout. |
| image_editB | Edit one local PNG/JPEG/WebP through PdhAPI. The reference image is uploaded. Uses paid quota. |
| image_multi_referenceB | Generate an image from 2-10 local reference images, uploaded together. Uses paid quota. |
| image_batch_editB | Edit up to 10 local images sequentially with one prompt. Each image uses paid quota. Stops on first failure and reports completed files. |
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: generation from text, editing a single image, multi-reference generation, batch editing, and server configuration. No overlap or ambiguity between them.
Most tools follow the image_ prefix with descriptive verbs (generate, edit, multi_reference, batch_edit). server_info deviates from the prefix but is still clear and uses consistent snake_case.
Five tools is an appropriate scope for an image generation/editing server, covering the primary workflows without bloat.
The surface covers generation, single edit, multi-reference, and batch operations. Missing a delete or quota-check tool, but these are not critical gaps given the local file handling and server_info.