
Deckbase Mcp Server
- deckbase/deckbase-web
Deckbase MCP is a MCP server that exposes Deckbase docs, template blocks, and project context to your agent over stdio.
About
The Deckbase MCP server connects your AI coding agent to Deckbase so it can fetch live documentation, pull curated template blocks, and understand project context without you copying files into the chat. developers who treat slides, one-pagers, and investor updates as part of the product ship cycle install it when they want the agent to draft or refactor narrative assets in sync with a Deckbase-backed source of truth. Transport is stdio via the published npm package, which matches how most local agent setups register MCP servers. It is a narrow integration—not a general presentation editor—but that focus keeps the tool surface small and predictable for day-to-day agent workflows. Use it during Build when you are producing docs, pitch materials, or internal specs that should mirror what lives in Deckbase. Skip it if you do not use Deckbase or only need generic markdown in-repo.
- 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
Deckbase Mcp Server by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add deckbase-mcp-server -- npx -y deckbase-mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | deckbase-mcp-server |
|---|---|
| Transport | STDIO |
| Auth | None |
| Repository | deckbase/deckbase-web ↗ |
What it does
Let your coding agent read Deckbase docs, reuse template blocks, and pull project context while you ship decks or product narratives.
Who is it for?
Best when you already use Deckbase and want Claude Code or Cursor to draft or update narrative assets with live context.
Skip if: Skip if you do not use Deckbase or only need in-repository markdown without an external deck platform.
What you get
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
By the numbers
- Server schema version 1.0.0
- Single npm stdio package: deckbase-mcp-server
- Repository: github.com/deckbase/deckbase-web
Recommended MCP Servers
How it compares
Deckbase MCP is a workspace integration, not a slide-design skill or generic document generator.
FAQ
Who is Deckbase MCP for?
and small-team developers 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.