ioBroker.mcp

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 (/mcp endpoint)
• 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:

1. Standalone (default) – it starts its own web server on the configured port. The MCP endpoint is http(s)://:/mcp.

2. 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 web instance 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
• MCP server URL: The address to enter in the MCP client, with a button to copy it. Standalone it is built from SSL, bind address and port of this instance; as a web extension from SSL, bind address and port of the selected web instance (with “all instances” one URL per instance). With OAuth and a Public URL the public URL is used, otherwise the host from the address of the admin page.

Authentication

• Enable Authentication: Enable ioBroker user authentication for the web server
• Default User: The ioBroker user whose permissions MCP requests run with when authentication is off (default: admin). With authentication on, every session runs with the permissions of the user who logged in, so this field is hidden then. All object/state reads and writes performed by the tools are executed in the name of that user, so the user’s ACLs are enforced. A plain name like operator is automatically expanded to system.user.operator. As a web extension the authentication and the default user of the web instance apply.

OAuth