openbot-mcp
Officialby openbotai
README.md
# openbot-mcp
`openbot-mcp` is the [Model Context Protocol](https://modelcontextprotocol.io) server for
[OpenBot.ai](https://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-mcp` does not select it. Only the `server_status` tool exists. Data audit,
> training readiness, Catalog and judgment tools are being designed.
## Run from source
```bash
pip install -e ".[dev]"
OPENBOT_MCP_ROOTS=/path/to/data openbot-mcp
```
Claude Code:
```bash
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:
```json
{
"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
```bash
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
TDQS
A3.9/5.0
Scored across 1 tool
Disambiguation5/5
Only a single tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
Naming Consistency5/5
With only one tool, naming is trivially consistent. The name follows a clean noun_noun pattern with no conflicting conventions.
Tool Count1/5
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.
Completeness1/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues