document-creation-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMFY_API_CFG | No | CFG scale. | 7.0 |
| COMFY_API_KEY | No | Optional bearer token for the ComfyUI endpoint. | |
| COMFY_API_URL | No | Base URL of the ComfyUI instance, e.g. http://comfyui:8188. | |
| COMFY_MCP_URL | No | Address of your running ComfyUI MCP server, e.g. http://comfyui-mcp:8000/mcp or .../sse. | |
| IMAGE_BACKEND | No | Image source backend: 'mcp' (ComfyUI MCP server) or 'comfy_api' (direct ComfyUI HTTP API). | mcp |
| COMFY_API_SEED | No | Seed (0 = random per request). | 0 |
| COMFY_MCP_TOOL | No | Name of the image tool in that server. | generate_image |
| COMFY_API_STEPS | No | KSampler steps. | 25 |
| COMFY_API_SAMPLER | No | KSampler sampler. | euler |
| COMFY_MCP_API_KEY | No | Bearer token sent as Authorization: Bearer <key> (if the server requires auth). | |
| COMFY_MCP_COMMAND | No | Only used if COMFY_MCP_URL is unset, to spawn a stdio subprocess. | |
| COMFY_MCP_TIMEOUT | No | Seconds to wait for image generation (both backends). | 300 |
| DOC_MCP_IMAGE_DIR | No | Where generated images are cached. | output/images |
| COMFY_API_WORKFLOW | No | Path to a JSON workflow template using placeholders. | |
| DOC_MCP_OUTPUT_DIR | No | Where .pptx files are written. | output |
| COMFY_API_SCHEDULER | No | KSampler scheduler. | normal |
| COMFY_MCP_TRANSPORT | No | Transport: 'auto', 'streamable-http', or 'sse'. | auto |
| COMFY_API_CHECKPOINT | No | Checkpoint loaded by the default workflow. | sd_xl_base_1.0.safetensors |
| COMFY_API_AUTODISCOVER | No | When enabled, auto-selects an installed checkpoint and valid sampler/scheduler. | true |
| DOC_MCP_DISABLE_IMAGES | No | Skip all image generation. | 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_themesA | List the available design theme names. |
| get_themeB | Return the full definition (colors, fonts, image style) of a theme. |
| generate_imageB | Generate a single image via the ComfyUI MCP server and return its local path. Args:
prompt: Base image description.
theme: Theme whose |
| list_comfy_modelsA | List models available on the ComfyUI HTTP API (checkpoints/samplers/schedulers). Useful to see what the direct |
| create_presentationA | Create a PowerPoint deck from a structured plan and return the file path. The orchestrating model is expected to do any web research and produce the
slide plan. { "title": "Deck title", "theme": "dark_tech", "output_filename": "my_deck", "slides": [ {"title": "Intro", "layout": "title", "subtitle": "An AI-generated deck"}, {"title": "Topic", "bullets": ["Point 1", "Point 2"], "image": {"prompt": "futuristic city", "target": "content"}}, {"title": "Deep dive", "layout": "image_full", "image": {"prompt": "abstract data flow"}} ] } Images declared with a |
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 distinct purpose: creating full presentations, generating images, retrieving themes, listing models, and listing themes. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_presentation, generate_image). No mixing of conventions.
Five tools is an appropriate scope for document creation, covering creation, image generation, and theme management without being excessive or insufficient.
Core workflows (create presentation, generate images, manage themes) are covered. Missing tools for updating or deleting presentations, but this is acceptable for a creation-focused server.