Yes, Simplisafe is free to use.

How do I install Simplisafe?

Simplisafe is a local plugin. Install it using npm package: simplisafe-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

What credentials does Simplisafe need?

Simplisafe requires the following credentials or environment variables: SIMPLISAFE_REFRESH_TOKEN. You can find setup instructions on the server detail page.

What AI apps work with Simplisafe?

Simplisafe uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Simplisafe MCP Server

by Chris Hall

Developer ToolsScan in ProgressLocalNew

Free

Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks

About

Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks

Security Report

0.0

Use Caution0.0Moderate Risk

10 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Remote servers are capped at 8.0 because source code is not available for review. The score reflects endpoint verification only.

What You'll Need

Set these up before or after installing:

OAuth refresh token from the one-time browser login (scripts/bootstrap-auth.mjs)Required

Environment variable: SIMPLISAFE_REFRESH_TOKEN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-simplisafe-mcp": {
      "env": {
        "SIMPLISAFE_REFRESH_TOKEN": "your-simplisafe-refresh-token-here"
      },
      "args": [
        "-y",
        "simplisafe-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

simplisafe-mcp

MCP server for SimpliSafe home security. Check whether the system is armed, review sensors and events, arm/disarm, and control smart locks — from Claude.

This server can disarm a home alarm and unlock doors. Every tool that changes physical state, plus the tool that reads alarm PINs, is gated behind an explicit confirm: true. Without it, no request is sent at all and you get a dry-run preview of exactly what would happen. Install it only where you'd be comfortable with that capability.

Developed and maintained by AI (Claude Code).

What you get

Tool
`simplisafe_list_systems`	Systems on the account with current alarm state
`simplisafe_get_system`	One system's state, connectivity, base-station messages
`simplisafe_list_sensors`	Sensors with battery / offline / triggered status, filterable
`simplisafe_list_locks`	Smart locks with locked / unlocked / jammed state
`simplisafe_get_events`	Recent base-station events (arm, disarm, opens, alarms)
`simplisafe_get_settings`	Entry/exit delays, volumes, base-station health
`simplisafe_get_pins`	Alarm PINs — cleartext, confirm-gated
`simplisafe_set_alarm_state`	Arm home / arm away / disarm — confirm-gated
`simplisafe_set_lock_state`	Lock / unlock a door — confirm-gated
`simplisafe_healthcheck`	Auth + API reachability

Supports SimpliSafe 3 systems. Legacy SS2 systems are rejected with an explanation rather than an opaque upstream 404.

Install

npm install -g simplisafe-mcp

Or add to .mcp.json:

{
  "mcpServers": {
    "simplisafe": {
      "command": "npx",
      "args": ["-y", "simplisafe-mcp"],
      "env": { "SIMPLISAFE_REFRESH_TOKEN": "${SIMPLISAFE_REFRESH_TOKEN}" }
    }
  }
}

Authentication — one browser login, once

SimpliSafe issues no API keys. The credential is an OAuth2 refresh token, minted by a browser login you perform one time:

git clone https://github.com/chrischall/simplisafe-mcp && cd simplisafe-mcp
node scripts/bootstrap-auth.mjs             # prints an authorize URL
# sign in (MFA included), then copy the com.simplisafe.mobile:// URL
node scripts/bootstrap-auth.mjs "<that URL>"

The token is written to .env (mode 0600) after being verified against the live API. SimpliSafe does not rotate refresh tokens, so it stays valid until you sign out of all devices in the SimpliSafe app — which is how you revoke it.

Capturing the code: open DevTools → Network and tick Preserve log before signing in; afterwards the browser fails to open a com.simplisafe.mobile://… link, and that failed entry's link address is what you paste. The code is single-use and expires in about two minutes.

Treat the resulting token like a house key: it grants full control of the alarm.

Writes are gated, and verified

Calling a write tool without confirm: true sends nothing and returns a preview, including a plain statement of the physical consequence:

{
  "dryRun": true,
  "action": "set alarm state to away",
  "method": "POST",
  "path": "/ss3/subscriptions/7858153/state/away",
  "currentState": "OFF",
  "warning": "Arms ALL sensors including interior motion. Starts an exit delay; anyone still moving inside when it expires can trigger the siren and a monitoring-center dispatch.",
  "note": "Nothing was sent. Re-run with confirm: true to execute."
}

With confirm: true, the tool executes and then re-reads the system to check what actually happened, reporting confirmed, in_progress (the exit delay is counting down), or unconfirmed. A 2xx is never treated as proof.

Hosted connector (optional)

The same tools can run as a Cloudflare Worker so they're reachable from claude.ai on the web, desktop and phone. This archetype supports it because auth is a non-rotating refresh token — no browser bridge, no signed-in tab.

The connector runs the whole OAuth bootstrap itself, as a two-step login page, so it doesn't depend on a local install and you never paste a long-lived credential. See docs/DEPLOY-CONNECTOR.md.

Shell access without the server

For quick one-off queries there's a curl-based skill in skills/simplisafe-api/ — same API, no MCP process, sharing the same refresh token.

Development

npm install
npm run build
npm test              # node suite
npm run worker:test   # Workers-runtime suite (connector)

Verified endpoint shapes live in docs/SIMPLISAFE-API.md, including several things that are easy to get backwards:

lock state is encoded 1 = locked, 2 = unlocked;
system version for routing is at location.system.version, not the top-level systemVersion;
events and doorlock control are not under the ss3/ prefix;
numEvents has an undocumented hard ceiling of 50;
settings.pins returns alarm codes in cleartext alongside harmless settings.

Disclaimer

Unofficial. Not affiliated with or endorsed by SimpliSafe. It uses the same private API the SimpliSafe mobile app uses, with your own account credentials. Use at your own discretion.