| FMRS | 62 / 100 · C | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 9 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - Individual learners already using Anki and AnkiConnect.
- Users who want AI-guided review, explanations, and dynamic card creation.
- Users connecting local Anki to Claude Desktop, Cursor, Cline, or Zed.
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
| - Q&A and research scenarios that need real-time, clean web content
- Users with an existing Exa account who want a zero-deployment remote option
|
|---|
| Not for | - Users without the Anki desktop application or AnkiConnect.
- Organizations requiring official Anki support or an official integration.
- Remote users seeking only review workflows; GUI tools are intended for editing and creation, not review sessions.
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
| - Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
- Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
|
|---|
| Required permissions | - Requires access to the configured AnkiConnect URL, which defaults to local http://localhost:8765.
- Write operations can create, modify, move, and delete Anki content; deletion tools require explicit confirmation.
- Media imports may read specified file paths or URLs, subject to media security settings.
- If AnkiWeb sync is enabled, the Anki application synchronizes directly with AnkiWeb.
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
| - Requires an Exa API key for full functionality; OAuth login is optional in remote mode
- web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
|
|---|
| Risks and side effects | - The project is explicitly in beta, and APIs and features may change.
- Deleting notes permanently removes associated cards; clearing tags, deleting media, and removing fields can also cause data loss.
- updateNoteFields may silently fail while the note is being viewed in Anki's browser.
- ngrok mode is unauthenticated, so anyone with the URL may reach Anki; the managed Tunnel requires login authentication.
- Remote HTTP exposure requires correct ALLOWED_HOSTS configuration; misconfiguration can cause rejected requests or broader exposure.
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
| - The API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
- agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
|
|---|
| Supported clients | Claude Desktop, Cursor IDE, Cline, Zed Editor | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 48 | 11 | 4 |
|---|