Log inSubmit server
Simplisafe MCP logo

Simplisafe MCP

Inspect and control SimpliSafe 3 alarms, sensors, events, settings, and smart locks through MCP with confirmation safeguards.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Simplisafe MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "simplisafe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "simplisafe-mcp"
      ],
      "env": {
        "SIMPLISAFE_REFRESH_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly (4d ago).

Overview

The simplisafe-mcp MCP server connects AI clients to SimpliSafe home-security accounts through the service's private API. It provides read access to alarm state, sensors, locks, events, settings, PINs, and connectivity, plus confirmed operations for alarms and smart locks. Authentication uses a SimpliSafe OAuth2 refresh token obtained through a one-time browser login. Reach for it when an agent needs to inspect or cautiously manage a SimpliSafe 3 system.

Use cases

  • Check whether a SimpliSafe system is armed
  • Review triggered, offline, or low-battery sensors
  • Inspect recent alarm and entry events
  • Arm or disarm a SimpliSafe 3 system with confirmation
  • Lock or unlock a connected smart lock with confirmation

Key features

  • SimpliSafe 3 system and connectivity status
  • Sensor battery, offline, and triggered-state queries
  • Alarm events, settings, and PIN retrieval
  • Confirmed alarm arm and disarm controls
  • Confirmed smart-lock control
  • Post-write state verification

Tools10

What Simplisafe MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 47d

What it can do

From the 10 tools this server returned when we ran it; 10 declare their own safety hints.

Can delete or modify data · 3Handles credentials · 4Makes network requests · 10Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age83 days
Maintainers1

Observed 2026-10-20 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · simplisafe-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads3kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Simplisafe MCP works

What simplisafe-mcp MCP server does

The simplisafe-mcp MCP server exposes SimpliSafe account and home-security operations through MCP. It can list systems and show a system's alarm state, connectivity, and base-station messages. Sensor queries include battery, offline, and triggered conditions, while lock queries report whether each smart lock is locked, unlocked, or jammed.

The server also retrieves recent base-station events, such as arming, disarming, openings, and alarms. Settings include entry and exit delays, volume values, and base-station health. A health check tests authentication and API reachability.

Write operations cover setting the alarm to home, away, or disarmed, and changing a smart lock to locked or unlocked. Reading alarm PINs is also treated as a sensitive operation.

How it works

The server communicates with SimpliSafe using the same private API used by the company's mobile app, authenticated with the user's OAuth2 refresh token. It supports SimpliSafe 3 systems and rejects legacy SS2 systems with an explanation rather than passing through an unclear upstream error.

Operations that can change physical state, along with PIN retrieval, require confirmation. Depending on the client, confirmation appears as a prompt or as a preview and one-time token that must be supplied on a subsequent call. The preview identifies the target and intended effect. Before executing a token-based action, the server checks that the relevant alarm or lock state and requested arguments still match the approved preview.

After a confirmed write, the server reads the system again. Its result distinguishes a confirmed change from an in-progress action, such as an alarm exit delay, or an unconfirmed result; a successful HTTP response alone is not treated as proof.

Setup and configuration

Install the package globally with npm or configure an MCP client to run it through npx. The server requires SIMPLISAFE_REFRESH_TOKEN in its environment.

SimpliSafe does not issue API keys for this integration. Create the refresh token with the repository's browser-login bootstrap script: open its generated authorization URL, complete sign-in and MFA, then provide the resulting com.simplisafe.mobile:// callback to the script. The token is verified against the live API and saved with restrictive file permissions. It remains valid until all devices are signed out in the SimpliSafe app.

Confirmation behavior can be adjusted with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, MCP_CONFIRM_TTL_SECONDS, and MCP_CONFIRM_SECRET. The last option is only needed when signed confirmation tokens must survive a server restart.

Tools and capabilities

The simplisafe-mcp MCP server includes these tool groups:

  • Account and state inspection: systems, one system, sensors, locks, events, settings, and health.
  • Sensitive reads: alarm PIN retrieval after confirmation.
  • Alarm control: home arm, away arm, and disarm after confirmation.
  • Lock control: lock or unlock a door after confirmation.

A separate curl-based skill in the repository can query the same API without starting an MCP process and uses the same refresh token.

Limitations and notes

This is an unofficial integration and is not affiliated with or endorsed by SimpliSafe. It uses private API behavior and should be installed only where granting alarm and door-lock control is acceptable. The refresh token should be protected like a physical house key.

Legacy SS2 systems are unsupported. SimpliSafe API details also include a hard limit of 50 for event retrieval, and alarm PINs are returned in cleartext when requested. A confirmation token expires according to its configured TTL, cannot be reused, and is refused if the approved action no longer matches the current state.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Simplisafe MCP

simplisafe-mcp is an MCP server that connects AI clients to SimpliSafe home-security accounts through the service's private API. Its main tools inspect systems, sensors, locks, events, settings, and health, and can confirm alarm arm/disarm and smart-lock actions. It supports SimpliSafe 3 systems and uses an OAuth2 refresh token.

Install it with `npm install -g simplisafe-mcp`, or configure an MCP client to run `npx -y simplisafe-mcp`. Set `SIMPLISAFE_REFRESH_TOKEN` in the server environment. The repository also provides a bootstrap script for obtaining that token through a browser login.

Authenticate it with a SimpliSafe OAuth2 refresh token, not an API key. Run the repository's browser bootstrap script, complete the SimpliSafe login and MFA flow, then pass the returned `com.simplisafe.mobile://` URL back to the script. The resulting token is verified against the live API.

Yes, alarm changes and lock changes require confirmation before anything is sent. Clients with confirmation prompts can show an approval dialog; other clients receive a preview and one-time `confirmToken`, and the action runs only after a later call supplies that token.

No, it supports SimpliSafe 3 systems only. Legacy SS2 systems are rejected with an explanation instead of being processed through the API.

Related MCP servers

All in Home Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSimplisafe MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/simplisafe-mcp?style=directory)](https://allmcps.com/mcp/simplisafe-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/simplisafe-mcp"><img src="https://allmcps.com/api/badge/simplisafe-mcp?style=directory" alt="Simplisafe MCP on AllMCPs" /></a>