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., "@openbot-mcp check the server status"
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.
openbot-mcp is the Model Context Protocol server for
OpenBot.ai. It lets AI agents such as Claude Code, Cursor and Claude Desktop
use OpenBot tools for physical AI data work.
Status: skeleton. PyPI has only the pre-release
0.1.0.dev0, published to reserve the name;pip install openbot-mcpdoes not select it. Only theserver_statustool exists. Data audit, training readiness, Catalog and judgment tools are being designed.
pip install -e ".[dev]"
OPENBOT_MCP_ROOTS=/path/to/data openbot-mcpClaude Code:
claude mcp add openbot -e OPENBOT_MCP_ROOTS=/path/to/data -- openbot-mcpOther MCP clients use the same command in their MCP configuration file:
{
"mcpServers": {
"openbot": {
"command": "openbot-mcp",
"env": { "OPENBOT_MCP_ROOTS": "/path/to/data" }
}
}
}Related MCP server: MCP Workspace Server
Variable | Required | Description |
| Yes, for local tools | Directories the server may read, separated by the OS path separator. Paths outside them, including symlinks that point outside, are rejected. |
| No | Where artifacts are written. Default |
| No | OpenBot API base URL. Default |
| No | Default |
| No | Default |
Local tools only read the directories in OPENBOT_MCP_ROOTS and only write to the output
directory. The server never modifies source data, never runs shell commands and collects no
telemetry.
pip install -e ".[dev]"
python scripts/check_version.py
pytest -v
ruff check src tests scripts
mypy src
python -m buildVERSION is the package version source of truth. To release, update VERSION and
CHANGELOG.md, verify locally, then publish a GitHub Release whose tag is v<version>. The
release workflow tests every supported Python, builds the distributions and publishes to PyPI
through a trusted publisher.
openbot-mcp: MCP server for AI agents.
openbot-data: local robot/ego data processing library.
openbot-sdk: OpenBot platform API client.
MIT
Report the OpenBot MCP server version and which local directories it may read.
Inputs: no named parameters. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
Only a single tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
With only one tool, naming is trivially consistent. The name follows a clean noun_noun pattern with no conflicting conventions.
A single trivial status tool is far too few for an MCP server that presumably should provide meaningful bot-related functionality. This is an extreme mismatch.
The server only exposes a status/version endpoint and does not provide any actual operations, data access, or workflow coverage. The surface is severely incomplete for any plausible domain.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Context and control for any AI. Agent identity, scoped access, and proof across tools.
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
