Switch Bot Mcp Server

Created By
yasu89a year ago
The SwitchBot MCP Server is a Model Context Protocol (MCP) server that provides a feature to control SwitchBot devices interactively using SwitchBotAPI.
Overview

What is SwitchBot MCP Server?

SwitchBot MCP Server is a Model Context Protocol (MCP) server that allows users to control SwitchBot devices interactively using the SwitchBotAPI.

How to use SwitchBot MCP Server?

To use the SwitchBot MCP Server, download the binary from the release page, obtain your SwitchBotAPI token and secret, and configure the server settings accordingly.

Key features of SwitchBot MCP Server?

  • Interactive control of SwitchBot devices
  • Ability to perform operations on multiple devices simultaneously
  • Use data from one device to control another device

Use cases of SwitchBot MCP Server?

  1. Operating multiple SwitchBot devices at once.
  2. Automating tasks by using data from one device to trigger actions on another.
  3. Integrating SwitchBot devices into larger automation systems.

FAQ from SwitchBot MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed for interactive control of devices.

  • How do I obtain the SwitchBotAPI token and secret?

Follow the Getting Started guide on the SwitchBotAPI GitHub page.

  • What tools are available in SwitchBot MCP Server?

Currently, tools include retrieving devices, checking device statuses, and turning devices on or off.

Server Config

{
  "mcpServers": {
    "switchbot": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--name",
        "switch-bot-mcp-server",
        "-e",
        "SWITCH_BOT_TOKEN",
        "-e",
        "SWITCH_BOT_SECRET",
        "yasu89/switch-bot-mcp-server:latest"
      ],
      "env": {
        "SWITCH_BOT_TOKEN": "<YOUR_SWITCH_BOT_TOKEN>",
        "SWITCH_BOT_SECRET": "<YOUR_SWITCH_BOT_SECRET>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yasu89
Star
1
Language
Go
License
MIT license
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago