The openHAB MCP Server connects Claude, Cline, and other MCP clients to a real openHAB smart-home instance over its REST API, giving AI assistants comprehensive read/write access to the hub instead of a thin read-only status view. Built by tdeckers (Community), it is community-built and best for API & Web.
by tdeckers (Community)
About
The openHAB MCP Server connects Claude, Cline, and other MCP clients to a real openHAB smart-home instance over its REST API, giving AI assistants comprehensive read/write access to the hub instead of a thin read-only status view. It covers four core openHAB building blocks: Items (list, get, create, update, delete, and update item state — the actual light/sensor/switch values), Things (list, get, create, update, delete, plus configuration status, enable/disable toggling, firmware status, and available firmware updates), Rules (list, get, create, update, delete, edit a rule's script action, and trigger a rule to run on demand), and Scripts (list, get, create, update, delete). That combination means an assistant can not only ask "is the living room light on" but also author and modify automation logic conversationally. Distributed as a Python 3.7+ project with a prebuilt multi-arch image published to GHCR (`ghcr.io/tdeckers/openhab-mcp`) — the fastest path is `podman run` or `docker run` with `OPENHAB_URL` and `OPENHAB_API_TOKEN` env vars (plus optional basic-auth username/password), defaulting to stdio transport or switching to `MCP_MODE=remote` for Streamable HTTP and SSE endpoints on the same container. Setup docs cover both Claude Desktop and Cline-in-VSCode configuration. Actively maintained, no license file declared, 26 GitHub stars.
Trust verdict
How grades are computed →Grade A (94/100, reliable) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance100/100 · weight 20
The repository has been pushed to or released within the last six months. — last push 2026-06-21.
- 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 tdeckers/openhab-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.
Installation
docker run -d --rm -p 8081:8000 -e MCP_MODE=remote -e OPENHAB_URL=http://your-openhab-host:8080 -e OPENHAB_API_TOKEN=your-api-token --name openhab-mcp ghcr.io/tdeckers/openhab-mcp:latestCategories
Works With
Frequently Asked Questions
What is openHAB MCP Server?
Who built openHAB MCP Server?
Is openHAB MCP Server free?
How do I install openHAB MCP Server?
What does openHAB MCP Server integrate with?
Repo Health
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
- 2mo ago
- Install
- docker
- Package
- 8081:8000
Quick Info
- Install Type
- docker
- Author
- tdeckers (Community)
- Categories
- 2
- Integrations
- 2
Related Servers
Fetch
Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.
Time
Time and timezone conversion capabilities for AI assistants.
21st.dev Magic
Create crafted UI components inspired by the best 21st.dev design engineers.
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.
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.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →