deckrun-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECKRUN_API_KEY | No | API key to unlock paid tier features like video, audio, and account tools. Get your API key at agenticdecks.com after subscribing. |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_slide_formatA | Fetch the authoritative Deckrun slide format specification. Call this first to learn all layout tags, Markdown syntax, and rules before writing slides. Returns JSON with layout_tags, surface_syntax, example_markdown, and limits. |
| generate_slide_deckA | Convert Deckrun Markdown into a PDF slide deck. Call get_slide_format first to learn the correct Markdown format. Then call this tool with the completed Markdown. Returns: url (public PDF, 90-day expiry), slug, slides (count), warnings (non-fatal notices to self-correct), schema_version. Limits: max 10 slides, 50 KB Markdown. Slides separated by --- on its own line. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Deckrun Free Skill Card | OpenClaw/ClawHub compatible skill YAML. Machine-readable capability declaration for agent registries and orchestrators. |
| Deckrun Free OpenAPI Spec | Trimmed OpenAPI 3.0 spec covering /free/generate and /health. Use to understand request/response shapes. |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one provides the format specification, the other generates the slide deck. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern: 'generate_slide_deck' and 'get_slide_format'. Conventions are uniform.
With only 2 tools, the server feels minimal. While it covers the core workflow (get format, generate), the count is low for a full-featured service, but not extreme.
The tool set covers the essential flow: fetch format then generate. However, it lacks tools for managing or revising decks, leaving notable gaps for repeated use.