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.

DimensionHome Assistant MCPTalk to your house. Your AI assistant connected to Home Assistant via MCP. 50+ tools, three transports, one bunx command.Firecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS58 / 100 · C75 / 100 · B
Reliability8 / 2013 / 20
Security and permissions14 / 2012 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2017 / 20
Setup experience10 / 2017 / 20
Best for
  • Users wanting deep AI integration with smart home
  • Privacy-conscious users needing local voice control
  • Developers looking for multiple deployment options (STDIO, HTTP, Docker)
  • Enthusiasts exploring AI-driven automation
  • 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 without a Home Assistant instance
  • Enterprises requiring official vendor support (community-maintained)
  • Users extremely averse to any remote hosting (though local voice processing available)
  • Users needing only basic functionality (other simpler MCP servers may be more appropriate)
  • 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 Home Assistant entity states (lights, climate, media, etc.)
  • Control device states (on/off, brightness, temperature, etc.)
  • Access history data, logs, and configuration
  • Execute automations, scenes, and notifications
  • Manage dashboards and to-do lists
  • 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
  • Token leak: long-lived access token could be abused for unauthorized control.
  • Configuration errors may result in unintended actions (e.g., turning off critical safety devices).
  • HTTP/WS transport requires JWT auth, but misconfiguration could expose the service.
  • Voice features may introduce additional security risks (e.g., microphone access).
  • 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, CursorClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools8211