Home Assistant MCP vs Slack MCP Server

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

	Home Assistant MCP MCP Servers	Slack MCP Server MCP Servers
Tagline	Open-source MCP server that lets any LLM control and observe a Home Assistant smart home in real time.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
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.	Free· Free / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
Model	—	—
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	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
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 reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
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	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
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 Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →