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.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS39 / 100 · D76 / 100 · B
Reliability4 / 2013 / 20
Security and permissions6 / 2014 / 20
Maintenance8 / 2018 / 20
Documentation9 / 2017 / 20
Setup experience12 / 2014 / 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.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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.
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Desktop, Cursor, VS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools715