This release is a pre-release and may not be stable for production use.
openbot-mcp
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.
Run from source
pip install -e ".[dev]"
OPENBOT_MCP_ROOTS=/path/to/data openbot-mcp
Claude Code:
claude mcp add openbot -e OPENBOT_MCP_ROOTS=/path/to/data -- openbot-mcp
Other MCP clients use the same command in their MCP configuration file:
{
"mcpServers": {
"openbot": {
"command": "openbot-mcp",
"env": { "OPENBOT_MCP_ROOTS": "/path/to/data" }
}
}
}
Configuration
| Variable | Required | Description |
|---|---|---|
OPENBOT_MCP_ROOTS |
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. |
OPENBOT_MCP_OUTPUT_DIR |
No | Where artifacts are written. Default ./openbot-output. |
OPENBOT_BASE_URL |
No | OpenBot API base URL. Default https://api.openbot.ai/v1. |
OPENBOT_MCP_REDACT_PATHS |
No | Default true: replace file paths with episode-relative ids in evidence sent to paid APIs. |
OPENBOT_MCP_PAID_TOOLS |
No | Default false: paid tools stay hidden until they are available. |
Data boundary
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.
Development
pip install -e ".[dev]"
python scripts/check_version.py
pytest -v
ruff check src tests scripts
mypy src
python -m build
VERSION 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.
Package boundaries
openbot-mcp: MCP server for AI agents.openbot-data: local robot/ego data processing library.openbot-sdk: OpenBot platform API client.
License
MIT
Release files for openbot-mcp 0.1.0.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openbot_mcp-0.1.0.dev0.tar.gz | 7.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openbot_mcp-0.1.0.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 kB
Release files / openbot_mcp-0.1.0.dev0.tar.gz
| Download URL | openbot_mcp-0.1.0.dev0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7abbcaedcf0e251dc8c2d80f87f4b075709886c585afad8a7f5542e02224053
|
|
BLAKE2b-256 checksum How to use checksums |
2d8581b7af9c06ab36b373988585fdaafec0288751cc9ddadeb955f1bcfd39d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / openbot_mcp-0.1.0.dev0-py3-none-any.whl
| Download URL | openbot_mcp-0.1.0.dev0-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6856ebb7f9bc19d1b34e041c555c271f9a998ba6d28d22f58b9fbf5e8ba53705
|
|
BLAKE2b-256 checksum How to use checksums |
2f54cc8941e2b8ba8caa8c70e308897182dfc7887db773e2ce3f1f344238e5ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log