Documentation
Docs
Technical reference for Deckbase integrations, APIs, and developer guides.
Reference
MCP Setup Guide
GuideConnect Cursor, Claude Code, VS Code, Windsurf, and other MCP clients to Deckbase.
MCP Server Reference
ReferenceFull reference for the Model Context Protocol server: endpoints, tools, resources, and authentication.
FSRS in Deckbase
ConceptHow Deckbase uses the Free Spaced Repetition Scheduler, retention targets, and daily review workflow.
Spaced Repetition Algorithms
ConceptHow SM-2, Leitner, fixed intervals, and FSRS schedule reviews — and why Deckbase uses FSRS.
Quick links
Quick start
curl -X POST https://www.deckbase.co/api/mcp \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"tools/list","id":1}'Replace YOUR_API_KEY with a key from your dashboard. For setup instructions, see the MCP setup guide.
API overview
Deckbase provides two integration paths: the MCP server for AI-assisted deck and card management, and direct REST API endpoints for programmatic access.
- Create, update, and delete decks and cards in batches
- Generate AI audio and images for cards via ElevenLabs and image models
- Export full deck data including block snapshots and metadata
- Build custom templates with flexible block layouts
- Receive webhook events for deck and card changes
Start here
Connect your MCP client
Use the setup guide to configure Cursor, VS Code, Claude Code, or another MCP-compatible client with Deckbase authentication.
Validate schema first
Before creating cards in bulk, inspect template schemas and required fields so generated records stay consistent.
Run staged batches
Start with small write batches, sample outputs, and scale only after card quality and duplicate rate look healthy.
Best practices
Treat card creation as an operational pipeline
Keep request logs, validate required template fields before writes, and spot-check generated cards before scaling batch size.
Define one canonical template strategy
For teams, define one canonical template strategy and one retry policy. This avoids duplicate prompt drift and makes incident response much faster when mapper rules change.
Follow the recommended reading order
Setup page first, MCP Server reference second, then production rollout checks. This path minimizes authentication mistakes and schema mismatch errors during card creation.
Document rules in your repo
If you are implementing team workflows, document your template rules and batch acceptance gates directly in your repo so future updates stay consistent.
Run a weekly operational review
Check recent write failures, template drift, and duplicate prompt rates before scaling automation volume.
Version your integration checklist
Keep your integration checklist versioned so onboarding new contributors does not require reverse-engineering previous MCP setup decisions.
Include a rollback runbook
When possible, include a short runbook for rollback and reprocessing failed batches so production updates remain safe even when templates evolve.
FAQ
What is the Deckbase MCP server?
The Model Context Protocol (MCP) server lets AI tools like Cursor, Claude Code, and VS Code read your docs, list decks, and create cards programmatically. It uses standard JSON-RPC over HTTP.
Do I need coding experience to use Deckbase MCP?
Basic familiarity with API keys and JSON helps, but you primarily interact through natural language prompts in your AI tool. The MCP server handles the technical details.
Which AI tools support Deckbase MCP?
Cursor, Claude Code, VS Code with the MCP extension, Windsurf, and any other client that supports the Model Context Protocol.
Is the Deckbase API free to use?
MCP and API access are included with Pro and VIP subscriptions. You can create API keys from the dashboard once subscribed.
How do I get an API key?
Go to the API keys page in your dashboard, click Create key, and copy the token. Use it as a Bearer token in the Authorization header.
For guides and articles, see Resources