srs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for the server (default: 8000) | 8000 |
| SRS_DB | No | SQLite database file path (default: './srs.db') | ./srs.db |
| DATABASE_URL | No | Postgres connection string (alternative to SRS_DATABASE_URL) | |
| MCP_TRANSPORT | No | Transport mode: set to 'stdio' for stdio transport, otherwise HTTP is used | |
| SRS_DATABASE_URL | No | Postgres connection string (alternative to DATABASE_URL) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_cardA | Author a new flashcard and schedule it. |
| due_cardsA | List cards due for review now (due <= now), soonest first. Optionally
filter by |
| grade_cardA | Record a review of a card. |
| list_cardsA | List cards (newest first) regardless of due date, for an overview.
Optionally filter by |
| edit_cardA | Edit a card's content without disturbing its schedule. Update any of
|
| suspend_cardA | Shelve a card: keep it (with its full history and schedule) but remove it from the due queue, so it won't surface in due_cards until unsuspended. Reversible, non-destructive alternative to delete_card for cards you're unsure about. Returns JSON {card_id, suspended}. |
| unsuspend_cardA | Un-shelve a previously suspended card, returning it to the review queue (it becomes due again per its existing schedule). Returns JSON {card_id, suspended}. |
| delete_cardC | Delete a card by id (reset / cleanup). |
| statsA | Summary of the card box: total cards, how many are due now, total
reviews, and the deck list. Optionally scope counts to one |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: adding, deleting, editing, listing, reviewing, grading, stats, suspending, and unsuspending cards. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., add_card, delete_card, grade_card. Names are predictable and readable.
9 tools is well-scoped for a spaced repetition system, covering all essential operations without bloat. Each tool earns its place.
Covers core CRUD, review workflow, statistics, and suspension. Missing explicit deck management (e.g., create/delete deck) but decks are manageable via card properties.