sila2-mcp
It exposes configured SiLA 2 servers as MCP tools for discovery, property reads, and command execution.
List configured servers and check whether each answers.
Describe a server’s features, commands, parameters, responses, properties, and errors.
Read a SiLA property value once, including observable properties.
Run SiLA commands, including observable commands with intermediate responses and timeouts.
Return results as JSON, with SiLA errors reported as structured failures.
Save binary responses to files instead of putting them in context.
Ask for user approval before commands when configured, with per-server and per-property confirmation policies.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sila2-mcp read the current temperature from the thermal cycler"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
sila2-mcp
An MCP server that exposes SiLA 2 servers as tools, so an MCP client (e.g. Claude Code) can read properties and send commands directly instead of writing a client script each time.
It is generic: the servers are listed in servers.toml, and each server's features are
discovered from the server itself (sila2 Python client), so no per-instrument code is needed.
Tools
Tool | Moves hardware? | What it does |
| no | The configured servers, their confirmation policy, and whether each answers now |
| no | Features, commands (observable or not, parameters, responses, errors), properties, custom data types and defined errors, and the confirmation policy. |
| no | Read a property once (asks first only if |
| may | Run a command after the user's approval (see below); an observable one is waited for and its intermediate responses collected |
| no | Forget the approvals remembered in |
Results are JSON. On failure ok is false and error holds the SiLA error
(e.g. a defined execution error's identifier and message). An unknown server, feature,
command or property, or a server that cannot be reached, is reported as a tool error with
its reason.
Binary values (images, videos, data files) are written to the output directory and
appear in the result as {"file": ..., "content_type": ..., "length": ...}, so they do not
enter the client's context. The content type comes from the FDL ContentType constraint,
otherwise from the file's leading bytes. The content reaches the model only if the client
opens the file afterwards (e.g. reads an image).
Related MCP server: proxy-mcp
Confirmation
Commands act on the physical world, so sila2-mcp itself asks the user before running them, through MCP elicitation (the client shows the question to the user; the model cannot answer it). The SiLA call runs only after an approval.
Mode | Behavior |
| Never ask |
| Ask each time |
| Ask with three choices: Decline; Accept "this time only" (asked again next time); Accept "this command for N minutes" (not asked again for that command for |
Defaults: commands once, property reads none, approvals kept for 30 minutes.
[confirm]
commands = "once" # none | every | once
properties = "none" # none | every | once
approval_ttl_minutes = 30 # or "unlimited" (until the MCP server restarts); --approval-ttl overrides
[servers.ardea]
# ...
confirm = { commands = "every" } # per-server override of the modesDeclined, dismissed, or not askable (the client has no form elicitation support): nothing is run and the result has
ok: false,error.type: "NotApproved"anderror.reasondeclined/dismissed/cannot_ask. A server that needs no confirmation (e.g. a simulator) must be set tononeexplicitly.The question puts the call in its first line (
Run MoveRelative(DeltaPan=30, DeltaTilt=0) on tapo?), since clients may show only the first lines.Claude Code shows the question in the terminal. The Claude Code VS Code extension currently declines every elicitation automatically (a client-side issue), so there nothing runs with
once/every; a decline cannot be told apart from a person's, hencedeclinedmeans "by the user, or automatically by the client". See issue #4 for per-client policies.Approvals live in the MCP server process: one session; restarting or reconnecting the server forgets them, and so does
revoke_approvals. Nothing lets the model grant an approval.On MCP 2026-07-28 connections the question travels as an
InputRequiredResultand the answer comes back in arequest_statesealed by the server (AES-GCM, per-process key), so a client cannot forge an approval; older connections useelicitation/create.Whether a question really reaches a person is up to the MCP client. A client that answers elicitations automatically defeats the confirmation; sila2-mcp cannot tell.
Every approval, refusal and executed command is appended to the audit log (
%LOCALAPPDATA%\sila2-mcp\audit.jsonl,~/.local/share/sila2-mcp/audit.jsonlelsewhere; top-levelaudit_log = "path"orfalsein the config).This is a software confirmation. It does not replace the physical safety measures of the instruments (interlocks, light curtains, emergency stops).
When the client shows the questions, call_command can be allowed in the MCP client's own
permissions, so the user is not asked twice. Do this only after checking that the questions
appear (see below).
Clients that cannot show the question (e.g. the Claude Code VS Code extension)
Signs: every command returns NotApproved with reason: "declined" although nobody declined
(no dialog appeared; the audit log shows declined within milliseconds of the call), or
reason: "cannot_ask".
Preferably, use a client that shows them. Claude Code in a terminal does, including the integrated terminal of VS Code: run
claudethere instead of using the extension's chat.Otherwise, let the client's permission prompt be the confirmation.
Use a configuration that does not ask, e.g. a copy of
servers.tomlwith[confirm] commands = "none" properties = "none"and register sila2-mcp with it:
claude mcp add -s user sila2 -- uv --directory /path/to/sila2-mcp run sila2-mcp --config /path/to/servers-noconfirm.tomlKeep
mcp__sila2__call_commandout ofpermissions.allow(and, to be explicit, list it inpermissions.ask), so that Claude Code asks before every command; allow only the reading tools:{ "permissions": { "allow": ["mcp__sila2__list_servers", "mcp__sila2__describe_server", "mcp__sila2__get_property"], "ask": ["mcp__sila2__call_command"] } }Do not use permission modes that may run tool calls without asking (e.g. auto mode, bypassPermissions) while instruments are connected: commands would then run with nobody asked.
What changes: the client asks once per call of
call_command, for every command alike (noonce, no "this time only"), showing the tool arguments (server, command, parameters). The audit log still records every executed command.The registration (
-s user) is shared by all Claude Code clients of the user, so the terminal then does not ask either. Switch back to the normal configuration when you use the terminal, or register the no-confirmation configuration with-s localin one project directory only (a local registration of the same name takes precedence there, for every client opened in that directory). Per-client policies are planned in issue #4.
Setup
uv syncEdit servers.toml (or point SILA2_MCP_CONFIG / --config at another file):
[servers.atc]
host = "127.0.0.1"
port = 5140
insecure = true # no TLS; for TLS set false and optionally root_cert = "path/to/ca.pem"
description = "Thermal cycler"Binary responses go to --output-dir, else $SILA2_MCP_OUTPUT_DIR, else a top-level
output_dir = "..." in the config, else %LOCALAPPDATA%\sila2-mcp\files
(~/.local/share/sila2-mcp/files elsewhere). Files are not deleted automatically.
Use with Claude Code
claude mcp add sila2 -- uv --directory /path/to/sila2-mcp run sila2-mcpUse it from Claude Code in a terminal, where the approval questions are shown (see Clients that cannot show the question for the VS Code extension).
The server talks MCP over stdio. Connections to the SiLA 2 servers are opened on first use and kept; after a SiLA 2 server restarts, the next failing call drops the connection and the following call reconnects.
License
MIT License. Copyright (c) 2026 RIKEN. See LICENSE.
Available Tools
4 toolscall_commandA
Run a SiLA 2 command and return its responses. MAY MOVE HARDWARE.
parameters maps parameter identifiers to values, e.g. {"BucketNumber": 1}.
An observable command is waited for until it finishes or timeout_s passes; its
intermediate responses are collected and returned. On failure, ok is false and
error holds the SiLA error (defined execution error identifier and message).
feature is needed only when two features of the server share the command name.
Inputs: server (required), command (required), feature, timeout_s, +1 more. Returns: object
describe_serverA
Describe one server's features: commands (observable or not, parameters, responses, intermediate responses, defined errors) and properties, with their FDL descriptions.
Read-only. Use it to learn parameter names and types before call_command.
Inputs: server (required). Returns: object
get_propertyB
Read a property's current value once (observable properties too).
Read-only. feature is needed only when two features of the server share the property name.
Inputs: server (required), property (required), feature. Returns: object
list_serversA
List the configured SiLA 2 servers and whether each one answers right now.
Read-only. Tries to connect to each server; a server that does not answer is reported with its error instead of failing the whole call.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct layer: list_servers for discovery, describe_server for introspection, get_property for reading a value, and call_command for execution. There is no meaningful overlap—describe_server describes schema while get_property returns a live value, and the descriptions make this clear.
All four names follow a clean verb_noun snake_case pattern (list_servers, describe_server, get_property, call_command). The convention is predictable and unambiguous.
Four tools map neatly onto the core SiLA 2 interaction loop (discover, inspect, read, execute), and each earns its place. It is on the lean side—no streaming or cancellation tool—but not thin for the essential scope.
The set covers discovery, introspection, property reads, and command execution with observable-command waiting and error reporting, which is a coherent lifecycle. Minor gaps remain: no subscription to observable property streams and no explicit command cancellation, but agents can work around these via repeated reads and timeouts.
Maintenance
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
Search, inspect and invoke every public tool on Invokera through one MCP connection.
Scans remote MCP servers for protocol, security, and TLS issues; exposes scan tools via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAggregates multiple backend MCP servers into a single unified interface with optional web management UI for tool control and configuration.195MIT
- FlicenseAqualityDmaintenanceUniversal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.7-
- FlicenseNot gradedqualityDmaintenanceExposes app-registered tools as an MCP server for OpenClaw, forwarding actual tool execution back to the app over a WebSocket bridge.-
- AlicenseNot gradedqualityBmaintenanceEnables aggregation, filtering, transformation, and composition of tools from multiple MCP servers through a single proxy with tool views.5AGPL 3.0