🌐

SwitchBot MCP

Updated June 2026No commits in 18 monthsTrust grade C66/100

The SwitchBot MCP, built by community, provides control SwitchBot smart home devices via the SwitchBot API — manage Bot switches, Curtain controllers, Color Bulbs, Plug Mini, Meter temperature and humidity sensors, Hub Mini, Lock, and Blind Tilt devices; query device status and sensor readings; trigger scenes and automations; control physical switches remotely; and integrate SwitchBot into comprehensive home automation workflows. It is community-built and best for API & Web.

Its repository has had no commits since February 2025 (18 months ago).

by community

No commits in 18 months

The last commit GitHub reports for this project is from February 2025. The repository is not archived and the maintainer may return. Treat it as feature-frozen and check the alternatives below before you depend on it.

About

Control SwitchBot smart home devices via the SwitchBot API — manage Bot switches, Curtain controllers, Color Bulbs, Plug Mini, Meter temperature and humidity sensors, Hub Mini, Lock, and Blind Tilt devices; query device status and sensor readings; trigger scenes and automations; control physical switches remotely; and integrate SwitchBot into comprehensive home automation workflows.

C
Mixed66/100
low confidence · 1 measured signal

Grade C (66/100, mixed) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.

What was measured

  • Repository maintenance15/100 · weight 20

    No push or release in over eighteen months. Nobody is patching this if the upstream API it wraps changes. — last push 2025-02-28.

  • Source verification100/100 · weight 25

    The repository URL was confirmed to resolve against the live GitHub API and is not archived.

  • Provenance65/100 · weight 10

    Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.

  • Listing ↔ repository match100/100 · weight 5

    The listing name lines up with the linked repository genm/switchbot-mcp.

What could not be measured

These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.

  • Live MCP handshakeunknown

    No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.

  • Measured uptimeunknown

    No probe history recorded for this server yet.

  • Tool-schema stabilityunknown

    Drift is a difference between two successive checks, and this server has none recorded.

Frequently Asked Questions

What is SwitchBot MCP?
SwitchBot MCP is an MCP server built by community. Control SwitchBot smart home devices via the SwitchBot API — manage Bot switches, Curtain controllers, Color Bulbs, Plug Mini, Meter temperature and humidity sensors, Hub Mini, Lock, and Blind Tilt devices; query device status and sensor readings; trigger scenes and automations; control physical switches remotely; and integrate SwitchBot into comprehensive home automation workflows.
Who built SwitchBot MCP?
SwitchBot MCP was built by community.
Is SwitchBot MCP free?
Yes, SwitchBot MCP has a free option. This MCP server is free and open-source. Check the GitHub repository for details.
How do I install SwitchBot MCP?
Install SwitchBot MCP from its GitHub repository: https://github.com/genm/switchbot-mcp
What does SwitchBot MCP integrate with?
SwitchBot MCP integrates with Claude Desktop, Cursor.

Repo Health

Quiet repo

Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.

Last commit
2y ago
Install
npm

Quick Info

Install Type
npm
Author
community
Categories
2
Integrations
2

Related Servers

🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local
📋

Time

Time and timezone conversion capabilities for AI assistants.

Local
💻

21st.dev Magic

Create crafted UI components inspired by the best 21st.dev design engineers.

Local
🌍

Apify MCP Server

The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.

Auth required
🌍

Browserbase MCP Server

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

Local

Sponsored

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →