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.

DimensionAgent RecallCorrection-first agent memory: the only open-source system that measures whether your agent actually stops repeating mistakes.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS57 / 100 · C75 / 100 · B
Reliability8 / 2013 / 20
Security and permissions10 / 2012 / 20
Maintenance12 / 2016 / 20
Documentation13 / 2017 / 20
Setup experience14 / 2017 / 20
Best for
  • Claude Code users who want their agent to stop repeating mistakes
  • Developers who want honest measurement of memory effectiveness
  • Privacy-conscious users requiring local storage
  • Teams adopting structured memory layers (episodic, semantic, procedural, etc.)
  • 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
Not for
  • Scenarios requiring real-time or high-throughput memory retrieval
  • Users wanting fully automatic memory management without manual session loop
  • Projects needing cloud sync or multi-user collaboration
  • Users requiring advanced retrieval performance like BM25 indexing
  • 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)
Required permissions
  • Read and write local filesystem (default path ~/.agent-recall/)
  • Execute local commands (e.g., CLI tools)
  • Optional: OpenAI API usage if OPENAI_API_KEY is set for vector search
  • Optional: Supabase mirror for remote sync
  • 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
Risks and side effects
  • Memory content may contain sensitive information; ensure access control despite local storage
  • The measurement instrument may produce misleading data (e.g., defaulted to "heeded" bias); interpret cautiously
  • The automatic session loop requires user compliance with session start/end protocols; otherwise memory may be incomplete
  • Experimental components (e.g., dream consolidation, recurrence harness) may be unstable
  • Dependency on npm package execution poses supply-chain risk (verify source)
  • 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
Supported clientsClaude Desktop, Cursor, Windsurf, VS Code, CodexClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools511