RokuMCP vs Simplisafe MCP

A side-by-side look at the RokuMCP and Simplisafe MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

RokuMCP logoRokuMCPHome Automation · Local subprocess (stdio)MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console63GoodAuth: not declaredSimplisafe MCP logoSimplisafe MCPHome Automation · Local subprocess (stdio)Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks61GoodAuth: not declared

Verdict: choose RokuMCP for home automation work as a local process; choose Simplisafe MCP for home automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

RokuMCP logoChoose RokuMCP when

  • You need dedicated capabilities in the Home Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: ROKU_DEVICE_HOST, ROKU_DEVICE_PASSWORD.
  • You want tools like roku_deploy, roku_delete_dev_channel, roku_discover.
Explore RokuMCP

Simplisafe MCP logoChoose 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.
Explore Simplisafe MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRokuMCP logoRokuMCPSimplisafe MCP logoSimplisafe MCP
CategoryHome AutomationHome Automation
Quality signal63/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsROKU_DEVICE_HOSTROKU_DEVICE_PASSWORDSIMPLISAFE_REFRESH_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars40
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools4210

Tools & capabilities

RokuMCP tools 42

  • roku_deploySideload (deploy) a Roku application to the device. Packages all files in the project directory and uploads them. A dev channel must not already be running, or it will be replaced.
  • roku_delete_dev_channelDelete the currently sideloaded developer channel from the Roku device.
  • roku_discoverScan the local network for Roku devices using SSDP discovery. Returns a list of all found devices with their IP addresses.
  • roku_keypressSend a single key press to the Roku device via ECP. Common keys: Home, Rev, Fwd, Play, Select, Left, Right, Down, Up, Back, InstantReplay, Info, Backspace, Search, Enter, Lit_<character>
  • roku_keypress_sequenceSend a sequence of key presses to the Roku device with an optional delay between each press.
  • roku_launchLaunch or deep-link into a channel on the Roku device. Use appId "dev" for the sideloaded developer channel.
  • roku_query_device_infoQuery the Roku device for its info: model, firmware version, serial number, network info, etc.
  • roku_query_active_appQuery the currently active (foreground) app on the Roku device.
  • roku_query_app_uiGet the current app UI tree as XML. Only works when a sideloaded dev channel is running.
  • roku_query_sg_nodesQuery SceneGraph nodes on the Roku device. Use type "all" for all nodes, "roots" for root nodes, or "node" with a nodeId to inspect a specific node.
  • roku_type_textType a text string into the currently focused text field on the Roku device. Each character is sent as an individual Lit_ keypress. Use this for search fields, email inputs, password fields, etc.
  • roku_query_media_playerQuery the media player state on the Roku device. Returns playback state (play, pause, buffer, stop, none), position, duration, and error info. Use this to verify video playback in tests.
  • +30 more on the listing page

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.

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.

RokuMCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "rokumcp": {
      "command": "npx",
      "args": [
        "-y",
        "roku-mcp"
      ],
      "env": {
        "ROKU_DEVICE_HOST": "YOUR_ROKU_DEVICE_HOST_HERE",
        "ROKU_DEVICE_PASSWORD": "YOUR_ROKU_DEVICE_PASSWORD_HERE"
      }
    }
  }
}

Simplisafe MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "simplisafe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "simplisafe-mcp"
      ],
      "env": {
        "SIMPLISAFE_REFRESH_TOKEN": "YOUR_SIMPLISAFE_REFRESH_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

RokuMCP is categorized under Home Automation and uses a local stdio subprocess. Simplisafe MCP belongs to Home Automation and uses a local stdio subprocess. Pick RokuMCP for home automation work and Simplisafe 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.

RokuMCP has no declared pricing — check the project's own site. Simplisafe MCP has no declared pricing — check the project's own site. 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 rokumcp and simplisafe-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, RokuMCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Simplisafe MCP has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.