ioBroker.mcpCAUTION
MCP server for ioBroker
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
MCP server for ioBroker
Description
This adapter exposes ioBroker as an MCP (Model Context Protocol) server, so MCP-capable clients (e.g. Claude Desktop) can read and control your installation through a well-defined set of tools.
Features
- MCP server over the Streamable HTTP transport (
/mcpendpoint) - Configurable HTTP/HTTPS web server
- Configurable port and bind address
- Optional authentication
- Optional SSL/TLS support
- Network diagnostics (ICMP ping / TCP probe) to troubleshoot adapter connections
- Adapter repository search to recommend installable adapters
Operating modes
The adapter can run in two ways:
- Standalone (default) – it starts its own web server on the configured port. The MCP endpoint is
http(s)://:/mcp.
- Web extension – it runs inside an existing `web` adapter
instance and shares its web server (port, authentication, SSL). Select the target web instance in the admin configuration ("Extend WEB adapter"). The MCP endpoint is then served under the web adapter, e.g. http(s)://:8082/mcp/.
When a web instance is selected, the standalone server settings (port, bind address, authentication, SSL) are hidden because they are inherited from the chosen web instance.
Configuration
The adapter can be configured through the ioBroker admin interface using JSONConfig:
Server Configuration
- Extend WEB adapter: Select a
webinstance to run as its extension. Leave empty to run standalone. - Port: The port on which the web server will listen (default: 8093) – standalone only
- Bind Address: IP address to bind the server to (0.0.0.0 for all interfaces) – standalone only
Authentication
- Enable Authentication: Enable ioBroker user authentication for the web server
- Default User: The ioBroker user
f69f814e81f7OBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add iobroker.mcp -- npx -y [email protected]
{
"mcpServers": {
"iobroker.mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (28)
18 read · 8 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
create_scene | write | |
create_state | write | |
delete_file | destructive | |
delete_object | destructive | |
file_exists | read | |
get_logs | read | |
get_object | read | |
get_states | read | |
history_query | read | |
list_adapters | read | |
list_devices | read | |
list_files | read | |
list_functions | read | |
list_hosts | read | |
list_instances | read | |
list_rooms | read | |
mkdir | read | |
ping_host | read | |
read_file | read | |
rename_file | write | |
search_adapter_repository | read | |
search_objects | read | |
set_object | write | |
set_state | write | |
set_states | write | |
system_info | read | |
write_file | write | |
write_log | write |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (4 observation(s))
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (6)
delete_file, delete_object
streamable-http
.mocharc.js
.releaseconfig.json
@iobroker/adapter-core, @iobroker/webserver, @iobroker/mcp-server, express, @alcalzone/release-script, @alcalzone/release-script-plugin-iobroker, @alcalzone/release-script-plugin-license, @iobroker/es
The MCP server is served at `POST/GET/DELETE /mcp` using the Streamable HTTP transport with per-session
Gates applied: no_behavioural_pass.
f69f814e81f7full audit observations/trust-audit/mcp-server/iobroker__iobroker.mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | f69f814e81f7 | CAUTION | B | 89 | first audit |
Questions
What is the ioBroker.mcp MCP server?
MCP server for ioBroker
What tools does ioBroker.mcp expose?
28 in total: 18 read-only, 8 that write, and 2 that can delete or overwrite (delete_file, delete_object). Every one is listed on this page with its risk.
Is ioBroker.mcp safe to connect to an agent?
With care. The audit graded it B (89/100) and found 6 things worth knowing before you trust this server, listed below with the exact line each was found on. Separately from the audit: 2 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does ioBroker.mcp need?
No credential environment variables were found in its source, so it appears to need none.
How does ioBroker.mcp run?
It speaks streamable-http, so it runs as a service you connect to over the network. It is published on npm as iobroker.mcp at 1.1.7.
How current is this page?
The grade is for one exact copy of the source (f69f814e81f7), read on 2026-10-11. The repository is watched and re-audited when it changes.