M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAnki MCP Server AddonSeamlessly integrate Anki with AI assistants via a local MCP server.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS55 / 100 · C75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions11 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Users who use Anki for spaced repetition and want to leverage AI to automate study workflows
  • Advanced users who need to manage cards, notes, and tags in bulk
  • Developers who want to integrate Anki data into AI workflows
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Casual users who don't need AI interaction and only want basic Anki features
  • Users uncomfortable with technical configuration who want plug-and-play
  • Users needing official support or enterprise-grade security guarantees
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read and modify Anki collection data (cards, notes, decks, tags)
  • Perform sync operations, communicating with AnkiWeb
  • Access and modify media files (import, delete)
  • Perform UI operations in Anki interface (e.g., open dialogs, browse)
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • Exposing via tunnel may increase unauthorized access risk, but built-in DNS-rebinding protection and optional API key mitigate it
  • Destructive tools (like field deletion) are hidden by default, but users can enable them, potentially causing data loss
  • Media file import has path traversal and SSRF risks, which are built-in validated, but loose configuration could lead to security issues
  • Automatic sync may unexpectedly overwrite or modify collection; regular backups recommended
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, Claude Code, OpenCodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools4111