The fundamental difference: your agent thinks in terms of content, not layout. PolyDocs handles the rest.
11 intents + 80+ content keywords automatically map to the right components. Tell your agent "create a pitch deck" and it knows exactly which 17 components to assemble.
Auto-detects executives, developers, investors, customers, students — and tailors component selection, density, and tone accordingly.
Startup (dark/teal), Corporate (navy/blue), Modern (near-black/green), McKinsey (navy/dark-blue), Keynote (white/Apple-blue). Each with unique fonts, spacing, and card styles.
Blueprint includes per-component image prompts. Integrates with ComfyUI to generate custom visuals automatically — hero images, section backgrounds, diagrams.
// User prompt "Create a pitch deck for my AI startup" // docforge_plan returns: Blueprint { components: 17 // cover, problem, solution, // market, traction, team... preflight: 3 // theme, font, density asset_prompts: 4 // hero + section visuals } // docforge_generate produces: DOCX // Word report with TOC PPTX // Rich slides with backgrounds HTML // Responsive web page
71 semantic components, 55 document profiles, 5 output formats — PolyDocs is the most complete MCP document engine available.
Business (14), Technical (8), Marketing (6), Education (5), HR (4), Finance (3), Product (4), AI/ML (4), Government (3), Sales (2), Executive (3), Creative (3), Documentation (4).
42 core + 20 analysis frameworks + 4 charts + 5 academic. Executive summary, SWOT, KPI dashboard, timeline, roadmap, architecture diagram, decision matrix, and more.
DOCX (with real Word TOC fields), PPTX (via PptxGenJS + python-pptx fallback), PDF (LibreOffice), HTML (responsive template), Markdown. One plan, any format.
4 configurable questions (theme, font, density, format). Agents ask before generating, ensuring the output matches user expectations every time.
Graphviz DOT→PNG pipeline for flowcharts, architecture diagrams, tree structures, Venn diagrams, and process maps. Embedded directly into DOCX output.
Output sandboxing (~/.docforge/output/), path traversal blocking, image URL allowlisting, HTML escaping, CSS validation, SSRF protection, temp auto-cleanup.
Recursive plan validation with typed errors (planning, IR, layout, render, theme, asset, export). Every error includes a machine-readable code and actionable suggestions.
Extend with custom components, export formats, themes, and asset providers. Drop-in Python files or entry-point packages. No fork required.
The entire pipeline from natural language to professional output in 4 steps.
User tells the AI agent what they need — "Create a quarterly business review deck" or "Write a technical architecture document".
The agent calls docforge_plan. PolyDocs returns a blueprint with matched components, preflight questions for the user, and per-slide image prompts for AI asset generation.
Agent asks the user about theme/font preference. If ComfyUI is available, generates custom visuals for each prompt. All data collected before the final step.
Agent calls docforge_generate with the filled plan and user choices. PolyDocs produces the final document — DOCX, PPTX, HTML, PDF, or Markdown — in seconds.
Every PolyDocs capability is exposed as an MCP tool. Compatible with every MCP client.
| Tool | Description |
|---|---|
| docforge_plan | Convert a natural language prompt into a structured Document Plan with profile matching, preflight questions, and asset generation prompts. |
| docforge_validate | Recursively validate a plan — checks component types, data schemas, children, style fields, and metadata. Catches errors before generation. |
| docforge_generate | Execute a plan and produce the final output file. Supports DOCX, PPTX, HTML, MD, and PDF formats. |
| docforge_component | Preview a single semantic component in any format. Useful for testing and iteration during development. |
| docforge_theme | List available themes with full colour palettes, typography specs, and visual previews. |
| docforge_describe | Get the full component catalog with data schemas and environment status. Helps LLMs understand available capabilities. |
| docforge_status | Check engine status — Node.js availability, component counts, format support, and theme registry. |
Every profile includes optimised component selection, layout rules, and formatting presets. No two documents are templated the same way.
Each theme is a complete design system with unique colours, typography, spacing, and card styles.
Teal / Dark · Inter · Left aligned
Blue / Navy · Georgia · Centered
Green / Near-black · Inter · Left aligned
Dark Blue / Navy · Georgia · Left aligned
Apple Blue / White · SF System · Centered
PolyDocs is hosted at polydocs.arcflameinteractive.com/mcp. Get a Application Token license, configure your client, and go.
// ~/.config/opencode/opencode.jsonc { "mcpServers": { "arcflame-polydocs": { "type": "remote", "url": "https://polydocs.arcflameinteractive.com/mcp", "headers": { "CF-Access-Client-Id": "<token from Arcflame>", "CF-Access-Client-Secret": "<token from Arcflame>" }, "enabled": true } } }
Compatible with Claude Desktop, opencode, Continue.dev, Cursor, Windsurf, and any MCP client. A Application Token license is required — issued upon subscription.
Request LicenseCloudflare-gated token licensing. Pay per call volume. Straightforward tiers.
From pitch decks to technical docs — PolyDocs turns natural language into professional documents. Get licensed and connect in minutes.