SuperAnki agents
MCP and GPT access for your decks, without exposing your whole account.
This page documents the agent surface that exists today. The auth model is real, deck-scoped, and explicit about what still needs backend wiring before writes can land in production.
MCP docs
Live
Published on this page for public discovery.
GPT schema
Live
Available at /api/openapi/gpt for custom GPT actions.
Deck tokens
Ready
Short-lived tokens can be minted server-side.
Deck writes
Ready
Validated card batches can be forwarded upstream.
MCP
Model Context Protocol access
SuperAnki's MCP surface is intended for trusted clients that need structured access to deck operations. The web slice ships the public contract and the same deck-scoped auth posture used by the GPT flow.
- Public MCP documentation with clear auth expectations
- Deck-aware workflows instead of broad account access
- Short-lived GPT token flow from a logged-in deck workspace
- OpenAPI action schema for GPTs and other agent runtimes
Current scope
The secure deck token flow and action schema are live now. If you want a richer MCP server, the next backend step is to map these validated deck-scoped requests onto the same trusted card-writing service used by GPT actions.
How it works
Secure by default
Step 1
Log in to SuperAnki
Use your regular web account so deck ownership can be checked server-side.
Step 2
Open a deck workspace
Generate a token from a specific deck. Tokens are scoped to that deck only and expire automatically.
Step 3
Connect your agent
Use the OpenAPI schema for a GPT or wire the MCP docs into your desktop client. Requests stay constrained and auditable.
GPT
Custom GPT setup
SuperAnki exposes a public OpenAPI schema for GPT actions at /api/openapi/gpt. The GPT still needs a user-generated Bearer token from a logged-in deck page before it can act.
Schema URL
https://superanki.app/api/openapi/gpt
Auth type
Bearer token, generated from a logged-in deck page
Action path
POST /api/gpt/decks/{deckId}/cards
Availability