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 MCP ServerVibe-code your Home Assistant setup from your IDE: automations, dashboards, themes and configs.NPM Sentinel MCP ServerAI-powered NPM package analysis MCP server
FMRS39 / 100 · D79 / 100 · B
Reliability4 / 2012 / 20
Security and permissions6 / 2016 / 20
Maintenance8 / 2018 / 20
Documentation9 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers who want to manage Home Assistant from AI-powered IDEs like Cursor, VS Code, or Claude Code.
  • Users who want to build and iterate on automations or dashboards using AI while retaining manual control.
  • Those who need robust, predictable API access to Home Assistant rather than SSH or ad-hoc scripts.
  • Developers auditing NPM dependencies within AI workflows
  • Teams performing supply chain security assessments
  • Users of Claude Desktop, Cursor, or VS Code
Not for
  • Users who do not want to install the HA Vibecode Agent add-on or do not want extra custom components inside Home Assistant.
  • Users who need direct REST API or WebSocket access to Home Assistant without the intermediary agent.
  • Beginners who are not comfortable installing Node.js locally or using MCP protocol.
  • Projects outside the NPM ecosystem (e.g., pure Python/Go)
  • Environments without network access to deps.dev, OSV.dev, and the npm registry
  • Scenarios requiring maintenance by an official upstream vendor
Required permissions
  • Requires access to the local file system (to run Node.js and npx).
  • Requires network access to the Home Assistant agent's port (usually 8099).
  • Requires environment variables HA_AGENT_URL and HA_AGENT_KEY for authentication.
  • The agent itself uses Home Assistant's SUPERVISOR_TOKEN to access internal APIs.
  • Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
  • Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
Risks and side effects
  • Storing the Agent Key in mcp.json may be leaked if committed to git.
  • AI-generated actions may modify or delete configurations, potentially causing data loss, though Git versioning mitigates this.
  • Relies on a custom agent running inside Home Assistant, which could introduce security vulnerabilities if exposed.
  • May inadvertently affect production environments if not configured carefully.
  • Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
  • Depends on availability and accuracy of external services
  • Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
  • Third-party open source project, not officially maintained by NPM or Anthropic
Supported clientsClaude Desktop, Cursor, VS CodeClaude Desktop, VS Code, Cursor
Tools719