mywebui-mcp

An MCP server for mywebui, the ioBroker SCADA/HMI visualisation. AI coding agents (Claude Code, Gemini CLI, OpenAI Codex, …) use it to list, read, check, create and update screens, custom controls and reports on a running ioBroker, to create projects, and to look up states to bind. It also gives the agent the mywebui development skills.

On the ioBroker side

mywebui ≥ 1.208.0. Admin → mywebui instance → AI agents (MCP):

• Allow AI agents (MCP): off by default.

• Dev projects (AI agents may write), e.g. dev, agent-test. Every other project is read-only.

• Allow AI agents to create projects: off by default.

Make a separate ioBroker administrator user for agents. The server signs in to web.0 with it. web.0 needs authentication switched on; without it, every call is refused. Behind a proxy, allow request bodies of 6 MiB (nginx: client_max_body_size; its default of 1 MiB answers 413).

No MCP command writes a state. Every write keeps the previous file in <project>/data/.mcp-backup/ (the newest 10 per document) and is recorded in the mywebui journal.

Related MCP server: GPT Plus Plus

What mywebui_write does not do

• Code in a written screen or control can write states with the rights of whoever opens the page. Script calls, two-way bindings and Simple Script write commands come back as a warning in the findings, not a refusal, so write only to dev projects and review the code before it goes to a plant project. The scan is a text heuristic and not a proof: a script that builds its call dynamically can escape it.

• An open designer tab does not reload the write, and a later save there overwrites it. Runtime pages of that project refresh; closed documents pick it up when opened.

• A report's output, schedule and trigger can only be set in the designer. A screen stays out of the multi-view index, and a control has no thumbnail, until it is saved in the designer.

Configuration

The server stops at start (exit code 2) when the address is unusable or there are no credentials. After a refused login (HTTP 400 or 401 from web.0) it does not try again for 60 seconds, because web.0 locks a user after repeated failures.

Keep the password in the agent's environment or secret store, never in a repository.

Connect an agent

Claude Code:

claude mcp add mywebui -e MYWEBUI_URL=https://scada:9090 -e MYWEBUI_USER=agent -e MYWEBUI_PASSWORD="$MYWEBUI_PASSWORD" -- npx -y @gokturk413/mywebui-mcp

-e stores the value in Claude's configuration file (~/.claude.json) in plain text, so use a dedicated agents' user whose password you can change.

Gemini CLI, ~/.gemini/settings.json:

{ "mcpServers": { "mywebui": { "command": "npx", "args": ["-y", "@gokturk413/mywebui-mcp"],
  "env": { "MYWEBUI_URL": "https://scada:9090", "MYWEBUI_USER": "agent", "MYWEBUI_PASSWORD": "$MYWEBUI_PASSWORD" } } } }

OpenAI Codex, ~/.codex/config.toml:

[mcp_servers.mywebui]
command = "npx"
args = ["-y", "@gokturk413/mywebui-mcp"]
env = { MYWEBUI_URL = "https://scada:9090", MYWEBUI_USER = "agent" }
env_vars = ["MYWEBUI_PASSWORD"]

env_vars forwards the variable from the environment that starts Codex; exporting it alone does not reach the server. NODE_EXTRA_CA_CERTS needs the same: env_vars = ["MYWEBUI_PASSWORD", "NODE_EXTRA_CA_CERTS"].

Tools

The skills are also resources: mywebui-skill://<skill>/<file>.

Licence

CC BY-NC 4.0, see LICENSE.