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.

DimensionWitsyDesktop AI assistant and universal MCP client for many model providersFirecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS45 / 100 · D75 / 100 · B
Reliability6 / 2013 / 20
Security and permissions8 / 2012 / 20
Maintenance11 / 2016 / 20
Documentation12 / 2017 / 20
Setup experience8 / 2017 / 20
Best for
  • Desktop users who want one interface for many model providers
  • Users who want to run Ollama models locally
  • Users needing desktop shortcuts, document retrieval, or agent features
  • Developers integrating desktop AI actions through a localhost HTTP API
  • 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
  • Users seeking a standalone MCP server that provides tools to other MCP clients
  • Users seeking a confirmed client-specific MCP server configuration
  • Users who do not want to configure cloud API keys or install a local model runtime
  • 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
  • Cloud models, search, generation, and speech services require the relevant API keys
  • Ollama requires a local installation and model files
  • Local-file RAG and the local filesystem plugin require access to selected files
  • Prompt Anywhere, AI commands, and global shortcuts interact with other desktop applications
  • The local HTTP API listens on localhost port 8090 by default, or the next available port
  • CLI installation may require creating system-level symlinks on macOS or Linux
  • 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
  • User-provided API keys are used with configured third-party services; costs and data handling depend on those providers
  • Local files, prompts, and conversations may be sent to the selected cloud models or services
  • The HTTP API is localhost-only by default; exposing it through a reverse proxy requires user-configured authentication
  • MCP servers, Python execution, agents, and local-file features can expand the actions or data accessible to the model
  • The software is licensed under AGPL-3.0
  • 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, VS Code, Cursor, Windsurf, Zed, Amp
Tools011