Grounded, safety-checked appliance operation packages for robots and agents. Zero-config trial.
mcp-name: cc.operandi/operandi
operandi_mcp_server.py exposes OPERANDI over the Model Context Protocol so any MCP-capable
agent host (Claude Desktop, Claude Code, or your own agent runtime) can identify an appliance and
pull its grounded, safety-checked, robot-executable operation package as native tools.
This is the "build for agents" surface: the customer is a robot's planner / an LLM agent, not a human reading PDFs.
| Tool | What it does |
|---|---|
identify_appliance | Resolve observed nameplate text / panel labels / model → a catalog object (call first). |
get_operation_package | The robot-executable package: model-exact procedures, control map + grounding, per-step verification signals, recovery state machine, safety envelope. |
list_appliances | Browse operable appliances (optionally by category). |
find_by_capability | Find appliances by function (heat / wash / brew / defrost …). |
A general model, cold, gives confidently-wrong physical instructions on ordinary appliances a large
fraction of the time (OPERANDI Stage A: 24% of cold instructions were would-fail, including
invented buttons and cycles). Grounded in the package these tools return, that fell to 0
hallucinations, 96% exact. The tools turn "guess the buttons" into "read the manufacturer's ground
truth". See ../docs/BUSINESS_MODEL.md.
pip install operandi-mcp
That's it. No key needed for your first packages: on first use the server mints an
instant trial key itself (POST /v1/trial — no signup, 2 operation packages included,
cached at ~/.operandi/mcp_key). When the trial is spent, tool responses tell the agent
exactly how to sign up free (10 packages/month) or go Pro.
Have a key already? Set it and it wins over the trial:
export OPERANDI_API_KEY=ok_live_...
{
"mcpServers": {
"operandi": { "command": "operandi-mcp" }
}
}
(Optionally add "env": {"OPERANDI_API_KEY": "ok_live_..."} once you have an account key.)
Then ask the agent: "Identify the Samsung ME20H705MSS and give me the safe procedure to defrost
0.5 kg of mince." — it will call identify_appliance then get_operation_package and answer from
grounded data.
OPERANDI_API_URL.Authorization: Bearer <key>; a missing/invalid key surfaces as a tool error, not a crash.pytest tests/test_mcp_server.py.Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx operandi-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"cc-operandi-operandi": {
"command": "uvx",
"args": [
"operandi-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceoperandi-mcppypicc.operandi/operandi works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.