Home Assistant MCP vs Sentry MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Home Assistant MCP MCP Servers	Sentry MCP MCP Servers
Tagline	Open-source MCP server that lets any LLM control and observe a Home Assistant smart home in real time.	Official Sentry MCP server: give Claude Code, Cursor, and other AI agents real access to your errors, traces, and triage.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (Apache 2.0). Self-hosted; only cost is your own Home Assistant instance and the LLM client you connect to it.	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month
Model	—	Bring-your-own LLM (OpenAI, Anthropic, Azure OpenAI, or OpenRouter) for natural-language search skills; agent-side model is whatever your MCP client runs.
Editorial score	—	—
Use cases	Conversational smart-home control from Claude Desktop or CursorLLM-driven Home Assistant automationsReal-time device state monitoring via SSEVoice-agent frontends that call HA servicesBulk add-on and HACS package management through chatPrototyping custom home-lab AI assistantsNatural-language climate and lighting scenesCamera snapshot and motion event triaging	Debug production error from IDE agentRoot-cause a latency regression via trace lookupTriage new issues (assign, resolve, comment) from chatCorrelate a failing test with recent Sentry eventsNatural-language search across eventsPost-deploy error-rate investigationPull stack trace and open the offending file for a fixSummarize top issues for a standupQuery self-hosted Sentry from an internal coding agent
Pros	Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD Token auth plus rate limiting on the bridge, so it isn't a trivially open control plane Apache 2.0 licensed, TypeScript, 500+ GitHub stars and active commits — reasonable community traction for an MCP project	Official first-party server from Sentry — kept in step with API changes, not a community wrapper Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx Works with self-hosted Sentry, not only sentry.io One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector Fine-grained skill toggles let you scope which tools the agent can call Covers the full debugging loop: issues, events, traces, search, and triage actions like assign/resolve/comment Open source, so the tool surface and prompts can be audited or extended
Cons	Requires a working Home Assistant instance and long-lived access token — not useful without one Self-hosted only; you own the reverse-proxy, TLS, and network exposure decisions Model-agnostic by design, so quality of device control depends heavily on which LLM client you attach Single-maintainer community project — issue triage and roadmap can be slower than vendor MCP servers Broad tool surface can flood an LLM's context window if you don't scope subscriptions to specific domains	You still need a paid Sentry plan to get useful volumes of events, retention, and org seats Natural-language search tools require you to bring your own OpenAI/Anthropic/Azure/OpenRouter key — extra cost and setup Value collapses if your team is not already invested in Sentry as its error/APM backend Remote server is single-tenant per token — sharing across a team means each engineer wires their own auth MCP itself is still young; some clients handle remote servers with headers imperfectly and stdio is often the fallback Read/write tools mean a misbehaving agent can resolve or reassign real issues — human-in-the-loop is not optional
Website	github.com	github.com

Pick Home Assistant MCP if

✅ Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
✅ Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
✅ Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
✅ Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD

Pick Sentry MCP if

✅ Official first-party server from Sentry — kept in step with API changes, not a community wrapper
✅ Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx
✅ Works with self-hosted Sentry, not only sentry.io
✅ One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector

Compare a different pair →