switch-bot-mcp-server

Provides an MCP (Model Context Protocol) server that lets an agent retrieve SwitchBot device lists and statuses and execute commands on SwitchBot devices using SwitchBotAPI credentials.

Evaluated Apr 04, 2026 (17d ago)
Repo ↗ Automation mcp switchbot iot automation home-automation go
⚙ Agent Friendliness
50
/ 100
Can an agent use this?
🔒 Security
52
/ 100
Is it safe for agents?
⚡ Reliability
24
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
55
Error Messages
0
Auth Simplicity
75
Rate Limits
10

🔒 Security

TLS Enforcement
70
Auth Strength
60
Scope Granularity
20
Dep. Hygiene
45
Secret Handling
60

Uses environment variables for SwitchBotAPI credentials (better than embedding secrets in code). The README does not describe transport security details, scope granularity, or how errors/logging handle secrets. MCP server likely bridges powerful device-control actions; without per-tool/user scoping, an agent with access to the server can execute commands broadly.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
35
Error Recovery
25
AF Security Reliability

Best When

You want an MCP-integrated automation agent to manage SwitchBot devices (read status, then execute device commands) using a single set of SwitchBotAPI credentials.

Avoid When

You cannot safely store/manage API tokens/secrets (SWITCH_BOT_TOKEN, SWITCH_BOT_SECRET) or you need strict auditability and per-scope authorization beyond what the MCP server offers.

Use Cases

  • Interactively control SwitchBot devices through an MCP-capable client (e.g., Claude Desktop)
  • Query device status and then conditionally execute actions
  • Batch/sequence operations across multiple SwitchBot devices

Not For

  • Highly sensitive environments requiring fine-grained authorization controls per action/user
  • Use cases needing a public REST/GraphQL API surface for direct programmatic access outside MCP clients
  • Workflows requiring guaranteed idempotency semantics for device control operations

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: SwitchBotAPI token + secret via environment variables
OAuth: No Scopes: No

Authentication is done by providing SWITCH_BOT_TOKEN and SWITCH_BOT_SECRET (per README). No OAuth or scope model is described at the MCP layer in the provided README.

Pricing

Free tier: No
Requires CC: No

No pricing information provided in the README.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Command execution tools may produce side effects that are not idempotent (be careful with retries).
  • Rate limiting/backoff behavior is not described in the README.
  • The server requires correct SwitchBotAPI credentials; failures will likely occur when tokens are missing/invalid.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for switch-bot-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered