anki-librarian-mcp
Related Servers
Alternatives to anki-librarian-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.1-
- AlicenseAqualityCmaintenanceEnables AI agents and assistants to work with a Databricks workspace — SQL, clusters and warehouses, notebooks, Jobs, Lakeflow pipelines, Unity Catalog, Volumes, dashboards, Genie, model serving, Vector Search, Lakebase and Apps — under a safety-first model with read/write/destructive/security classification, confirmation steps for dangerous changes, production resource protection, and a fully read-only mode. Every call is checked against the official Databricks SDK, returns typed schemas and redacted secrets, and unsupported features report an explicit error rather than faking results.45Apache 2.0
- AlicenseBqualityAmaintenanceEnables LLM agents to query databases with read-only access, while requiring human approval for writes through a token-based confirmation system.6GPL 3.0
- AlicenseAqualityAmaintenanceEnables LLMs to safely explore, query, diagnose, and modify relational databases through a unified set of schema introspection, SQL execution, and administration tools. Supports multiple database backends with AST-level read-only guards, automatic LIMIT injection, and explicit opt-in write permissions for DML and DDL.6Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI agents to inspect database schemas and run strictly read-only SQL queries with guardrails against destructive statements, multi-statement chaining, and unbounded scans. Supports SQLite natively and PostgreSQL optionally.4363 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM clients to safely explore SQLite databases through schema discovery, sampling, read-only querying, and query-plan analysis, with schema resources and an analysis prompt.8 npmMIT
TDQS
Scored across 13 tools
Each tool targets a distinct action and resource: read tools (list_decks, find_notes, get_notes), propose tools for different mutations (add notes, add cloze, update, create deck, delete, set due date, flag), and plan lifecycle tools (list_plans, apply_plan, reject_plan). find_notes (search excerpts) vs get_notes (full fields) are clearly separated, and the propose_* tools differ by object and operation.
Strong, predictable verb_noun pattern throughout, with a consistent propose_* prefix for dry runs and matching apply_plan/reject_plan lifecycle verbs. Minor deviations like singular vs plural (propose_update_note vs propose_add_notes) keep it just short of perfect.
13 tools is well-scoped for the Anki domain. The propose/apply split is intentional and each tool earns its place by covering a specific mutation or query without redundancy.
Covers a full lifecycle: deck/note discovery, note and cloze creation, updates, deletion, scheduling, flagging, and plan management. Minor gaps like moving notes between decks or deleting decks are absent but not blocking for core workflows.