@decken/mcp
Official# `@decken/mcp` — Official MCP Server & Agent Skill
Turn **Claude Code**, **OpenAI Codex**, **Cursor**, and **Windsurf** into a **better Gamma** via Decken's Native OpenXML (`.pptx`) Slide Generation Kernel (`POST /v1/decks`).
## 1-Command Setup
### Claude Code
```bash
claude mcp add decken -e DECKEN_API_KEY="$DECKEN_API_KEY" -- npx -y github:decken-ai/decken-mcp
npx skills add decken-ai/decken-mcp
```
### OpenAI Codex (`~/.codex/config.toml`)
```toml
[mcp_servers.decken]
command = "npx"
args = ["-y", "github:decken-ai/decken-mcp"]
env_vars = ["DECKEN_API_KEY"]
```
## Primary Unified Tool: `decken_generate`
- **Scenario 1 (`from_outline`)**: Pass `outline` (Markdown or slide array with `diagram` flows and `table` matrices) + `outputPath`.
- **Scenario 2 (`from_outline_with_reference`)**: Pass `outline` + `reference` (local path or `https://` URL to a corporate `.pptx` template OR reference `.png`/`.jpg` slide) + `outputPath`.
- **Scenario 3 (`improve_material`)**: Pass `source` (rough `.pptx` deck OR slide screenshots/renders) + optional `prompt` + optional `reference` + `outputPath`.
Also exposes `decken_reconstruct_slide`, `decken_reconstruct_deck`, `decken_compare_models`, `decken_job_status`, `decken_list_jobs`, and `decken_capabilities`.
## License
MIT
TDQS
Scored across 7 tools
decken_capabilities, decken_list_jobs, and decken_job_status are clearly distinct, but decken_generate is explicitly a 'Unified Slide Kernel' whose third mode (upgrade/reconstruct from source images) overlaps directly with decken_reconstruct_slide and decken_reconstruct_deck. decken_compare_models also performs diagnostic reconstruction, so an agent with a slide image has three plausible entry points and must rely on description nuance to choose.
All tools share a consistent decken_ snake_case prefix with an action-oriented suffix (generate, reconstruct_slide, reconstruct_deck, compare_models, list_jobs, job_status). Minor deviations exist: decken_capabilities is a bare noun and decken_job_status is a noun phrase rather than verb_noun, but the pattern is otherwise predictable and readable.
Seven tools is a well-scoped surface for a deck-generation service: capabilities discovery, three generation/reconstruction paths, model comparison, and two job-management tools. No tool is obviously redundant enough to be removed given the async job model.
The core lifecycle is covered: discover capabilities/models, submit generation or reconstruction jobs, poll status/list jobs, and download the resulting .pptx or preview via decken_job_status. Minor gaps exist around job control and asset management, such as cancelling/deleting jobs, listing available reference templates, or a dedicated download endpoint separate from status.