Simplisafe MCP vs Homeassistant MCP
A side-by-side look at the Simplisafe MCP and Homeassistant MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Simplisafe MCP for home automation work as a local process; choose Homeassistant MCP for home automation. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Simplisafe MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SIMPLISAFE_REFRESH_TOKEN. - You want tools like
simplisafe_list_systems, simplisafe_get_system, simplisafe_get_settings.
Choose Homeassistant MCP when
- You need dedicated capabilities in the Home Automation domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
HASS_HOST, HASS_TOKEN, HASS_SOCKET_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 61/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | SIMPLISAFE_REFRESH_TOKEN | HASS_HOSTHASS_TOKENHASS_SOCKET_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 576 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Simplisafe MCP | View Homeassistant MCP |
Tools & capabilities
Simplisafe MCP tools 10
simplisafe_list_systemsList the SimpliSafe systems on this account with their current alarm state (off/home/away), alarming status, connectivity and power status. Start here to get the `sid` other tools take.simplisafe_get_systemGet the current state of one SimpliSafe system: alarm state, whether it is alarming, base-station connectivity, power/battery status and any pending base-station messages.simplisafe_get_settingsGet base-station settings for a system: entry/exit delays, alarm volume and duration, door chime, voice prompts, plus base-station health (wifi/cellular signal, wall power, backup battery, RF jamming). Does not include PINs — use simplisafe_get_pins for those.simplisafe_get_pinsRead the system's user PINs (master, duress and named users). These are the live alarm codes and are returned in cleartext, so calling this puts them into the conversation. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a warning preview and a confirmToken and fetches nothing, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).simplisafe_list_sensorsList the sensors and devices paired to a system — entry sensors, motion, glass break, smoke/CO, keypads, sirens and locks — with battery, offline and triggered status. Filter by type with `type_name` (e.g. "entry", "motion_v2", "lock").simplisafe_list_locksList the smart locks on a system with their current state (locked / unlocked / jammed), lock and keypad battery status, and keypad connectivity. Returns the `serial` that simplisafe_set_lock_state takes. Polls the base station fresh by default, because a stale answer to "is my door locked?" is worse than a slow one.simplisafe_get_eventsGet recent events recorded by the base station — arm/disarm, sensor opens, lock and unlock, alarms, errors — newest first. Each event carries an ISO timestamp alongside the raw epoch seconds.simplisafe_set_alarm_stateArm or disarm the alarm system: "off" (disarm), "home" (perimeter only) or "away" (all sensors). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). This physically changes a security system: disarming leaves the house unmonitored, and arming can trigger a siren and a monitoring-center dispatch. After executing, the new state is verified by re-reading the system.simplisafe_set_lock_stateLock or unlock a SimpliSafe smart lock. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Unlocking physically opens a door lock, so it is gated even though it is technically reversible. After executing, the result is verified by re-reading the lock state.simplisafe_healthcheckCheck that the server can authenticate to SimpliSafe and reach the API. Reports whether the refresh token is configured and working, the resolved user id, and how many active systems the account has. Start here when other tools fail.
Homeassistant MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Simplisafe MCP
{
"mcpServers": {
"simplisafe-mcp": {
"command": "npx",
"args": [
"-y",
"simplisafe-mcp"
],
"env": {
"SIMPLISAFE_REFRESH_TOKEN": "YOUR_SIMPLISAFE_REFRESH_TOKEN_HERE"
}
}
}
}
Homeassistant MCP
No confirmed install command for Homeassistant MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Simplisafe MCP is categorized under Home Automation and uses a local stdio subprocess. Homeassistant MCP belongs to Home Automation and uses an install path we have not confirmed yet. Pick Simplisafe MCP for home automation work and Homeassistant MCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Homeassistant MCP has no confirmed install command yet — follow its own setup instructions.
Simplisafe MCP has no declared pricing — check the project's own site. Homeassistant MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add simplisafe-mcp and tevonsb-homeassistant-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Simplisafe MCP has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Homeassistant MCP has 40/100 (Fair) with 6 views, 0 installs and 576 GitHub stars.