Give agents tools, not unlimited motion authority.
The CenterOS MCP server lets an AI agent read the hardware catalog, fleet, sessions and datasets. Motion goes through the robot's safety profile.
centeros-mcp 0.1.0 · Developer preview
One block of config.
Point your MCP client at centeros-mcp and give it your token.
mcp.json
{
"mcpServers": {
"centeros": {
"command": "centeros-mcp",
"env": { "CENTEROS_TOKEN": "<your token>" }
}
}
}Tools
- list_hardware_catalog
- get_hardware_entry
- list_robots
- get_robot_twin
- fleet_overview
- list_fleet_alerts
- list_teleop_sessions
- get_teleop_session
- get_post_event_report
- send_robot_command
- get_safety_profile
- list_active_estops
- emergency_stop
- start_rc_sim
- rc_sim_status
- list_slam_sessions
- list_missions
- browse_datasets
- search_wiki
- list_available_actions
- centeros_action
How motion is gated
- Each command is checked against the safety profile for that robot kind
- Velocity commands are clamped to the profile limits, and the agent is told when that happened
- Commands are refused while an e-stop is active
- Tools available to a token depend on that account's permissions