Before write
Verify deckId, templateId, and required block IDs with list_decks/list_templates/get_template_schema.
Add the Deckbase MCP server to your AI tool to read docs and manage flashcard decks — directly from your coding environment.
Flashcards + MCP: same decks sync to the Deckbase app and mobile. For positioning vs other MCP servers and card workflows, see MCP for flashcards or the AI flashcard maker overview.
Available tools
Select your tool
One-click install — then add your API key in Cursor Settings → MCP.
Add to CursorOr add manually — open Cursor Settings → MCP → Add new global MCP server and paste:
{
"mcpServers": {
"deckbase": {
"url": "https://www.deckbase.co/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with a key from the dashboard. API keys don't expire. On 401, verify the header is Authorization: Bearer YOUR_API_KEY.
Treat Deckbase MCP as a production integration, not only a prompt convenience layer. Teams that run schema preflight checks, staged writes, and post-write sampling usually keep card quality high while scaling throughput. Teams that skip these steps often see duplicate prompts, malformed fields, and unnecessary review fatigue.
Verify deckId, templateId, and required block IDs with list_decks/list_templates/get_template_schema.
Use small batches first and apply dedupe checks to front-side prompt text before create_cards.
Sample new cards for clarity and retention suitability before increasing batch size.
Review failed records, patch mapper rules, and document one quality improvement for next run.
If you need implementation-level details for tools and parameters, use theMCP server reference.
For teams, standardizing this checklist as a shared runbook usually improves card quality consistency and reduces avoidable reruns.
Need an API key?
Create one in the dashboard — keys don't expire.