Deckbase Mcp Server
Let your coding agent read Deckbase docs, reuse template blocks, and pull project context while you ship decks or product narratives.
Overview
Deckbase MCP is a Build-phase MCP server that exposes Deckbase docs, template blocks, and project context to your agent over stdio.
What is this MCP server?
- Stdio MCP server (npm package deckbase-mcp-server v1.0.0)
- Exposes Deckbase documentation to Claude Code, Cursor, and other MCP clients
- Surfaces reusable template blocks for faster deck and doc assembly
- Provides project context so agents stay aligned with your Deckbase workspace
- Open-source repo: deckbase/deckbase-web on GitHub
- Server schema version 1.0.0
- Single npm stdio package: deckbase-mcp-server
- Repository: github.com/deckbase/deckbase-web
What problem does it solve?
Agents cannot see your Deckbase templates or project context unless you manually paste exports into every session.
Who is it for?
Indie builders who already use Deckbase and want Claude Code or Cursor to draft or update narrative assets with live context.
Skip if: Teams that do not use Deckbase or only need in-repository markdown without an external deck platform.
What do I get? / Deliverables
After registration, the agent can query Deckbase-backed docs and blocks so deck and doc work stays consistent with your workspace.
- Agent-readable Deckbase documentation snippets in chat
- Reusable template block references for decks and docs
- Project-aligned context for narrative and spec edits
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server wires an external content system into the agent during implementation and documentation work, not during early ideation alone. Docs is the best fit: primary value is structured documentation, reusable template blocks, and project-scoped context agents need when writing or aligning deliverables.
How it compares
Deckbase MCP is a workspace integration, not a slide-design skill or generic document generator.
Common Questions / FAQ
Who is Deckbase MCP for?
Solo and small-team builders who use Deckbase and want their AI agent to read docs, templates, and project context from that platform.
When should I use Deckbase MCP?
Use it during Build when you are writing specs, pitch decks, or internal docs that should match your Deckbase library and project settings.
How do I add Deckbase MCP to my agent?
Install the npm package deckbase-mcp-server, add a stdio MCP entry pointing at that binary, and configure any Deckbase credentials your setup requires per the deckbase-web repo.