The device exposes its AI assistant tools to external AI applications through the Model Context Protocol (MCP). Instead of chatting in the device's panel, you work from Claude Desktop, Claude Code, ChatGPT or any MCP-compatible client, and the client reads and acts on the device through the same tools, the same rights and the same permission cards as the built-in assistant.
Typical uses: ask Claude Desktop to compare several devices, keep a long engineering conversation with your own documents and the device data side by side, or let a client you already use drive the device during commissioning.
MCP requires the AI Connect or FULL licence on the device, unless the connecting person brings their own seat or credits. See credits and licences.
https://ai.Weble.ch/b/<id>, where <id> is a stable, opaque identifier of the device.wbox_request_control and a Takeover (MCP) card appears in the panel. Accept it. The client now pilots the device.Authorisations created this way are revoked automatically after 7 days without use. You can revoke them at any time from the MCP sessions list.
Instead of the Authorize card, create a token yourself: MCP sessions › New token, choose a label and an expiry (90 days by default, 30 days, 1 year or none). The token is shown once; copy it immediately. Paste it in the client's authorisation page when it asks for it, or send it as a Authorization: Bearer header with a client that supports it. Manual tokens idle for 60 days are revoked automatically.
A client configured with the generic URL https://ai.Weble.ch/mcp is not bound to one device. It first calls wbox_connect with the device's name, MAC address, VPN name or per-box URL; a Connection to this box (MCP) card then appears in that device's panel for approval. This lets one connector reach every device you manage.
Connectors configured with the former address mcp.ai.Weble.ch no longer work. Open the External client (MCP) menu of the device, copy the new URL and add the connector again.
Only one client pilots a device at a time. While a client has control:
Control ends when you take it back, when the client disconnects or goes idle, or when it releases it. Until control is granted, the client can only read documentation, check its status and request control.
MCP clients obey the same permission model as the built-in assistant, see permissions. A write requested by Claude Desktop raises the same permission card in the device's panel; the call waits about 45 seconds for your click, then fails if nobody answers. Rights are bounded by the role of the user who authorised the connector.
Two read-only guarantees exist for cautious setups:
peers_read tool refuses anything that is not classified as a read;
| Tool | Description |
|---|---|
peers / peers_read |
Call the device API: gateways, addresses, routes, loggers, logic, alarms, system, network. peers_read is strictly read-only. |
getDoc |
Local API documentation. |
boxDiagnostic, networkDiagnostic |
Read-only device sweep; ping, traceroute, interfaces, process logs. |
dataTransform |
Server-side computation on data or on conversation files. |
searchConversations, wbox_chat_history, wbox_chat_post, wbox_push_history |
Read the device's conversations, post into the journal. |
proposePlan, setWriteScope |
Plan cards; self-imposed write perimeter. |
runScript, saveScript, cancelScript, scriptList, scriptLogs, listSavedScripts, getSavedScript |
Sandbox scripts, same consent flow as in the panel. |
generateLogicBloc |
Build a custom logic block from a script. |
download, fileProfile, readFile |
Deliver files to the user; inspect conversation files. |
backupBox, restoreBox |
Backup to the browser; guided restore with confirmation. |
adsProjectSymbols, matchTags, modbusFrameTable |
SCADA and PLC mapping tools. |
browser |
The assistant's headless browser on the device's web interface, with the same card and pill as in the panel. |
wbox_connect, wbox_status, wbox_watch, wbox_request_control, wbox_licence |
Connector management: target a device, poll its state, request or release control, attach a credit licence. |
Streaming and direct file delivery of the peers tool are available in the device panel only.
Every MCP authorisation is recorded on the device first, in a local store with its label, creation date and owner; the Weble server only keeps a hashed copy of the token. At each connection the device sends its list of active tokens and the server aligns on it. Revoking on the device is therefore immediate and final, even if the server copy were out of date.
The MCP sessions list shows each token with its label, last use, expiry and a Revoke button, grouped by client with Revoke all.
Tool calls made by an MCP client are metered like assistant turns:
| Situation | Charged |
|---|---|
| The connecting person has a seat licence | nothing |
| The device has AI Connect or FULL | nothing |
The person attached their own credit licence with wbox_licence |
the person's credits |
| The connection was approved at the device's expense | the device's credits |
| None of the above | the call is refused |
The metered amount is a service share of what the tool result would cost as model input, since the model itself runs in the client.
https://ai.Weble.ch/mcp or https://ai.Weble.ch/b/<id>, MCP streamable HTTP: one POST per JSON-RPC message, optional text/event-stream presence channel, session header assigned at initialisation. Protocol versions 2024-11-05 to 2025-11-25 and later are accepted. No local or LAN endpoint exists on the device: all MCP traffic goes through the Weble cloud, whether the device is on the VPN or on a public address.claude_desktop_config.json entry or stdio bridge is needed or provided: the connector is a remote server added in the Connectors settings.
| Page | Description |
|---|---|
| AI assistant | The built-in assistant, credits, models, permissions. |
| AI driver | Unattended assistants on the device. |