Developers

Build robots from Claude, Cursor or your own code

Everything in Esos goes through one API. The Esos MCP server puts it in your AI assistant: describe a robot, change it, run its tests and publish it, in a chat.

The Esos API and MCP server open with the Studio. Join the waitlist to get a token in the first wave.

How it works

  1. 1

    Create a token

    In Esos, Settings → API tokens. It works in one workspace.

  2. 2

    Add Esos to your assistant

    One line for Claude Code, a few for Cursor.

  3. 3

    Ask

    “Create a café robot called Foxy, add arms, run the tests, publish it.”

Setup

Claude Code, over HTTP (nothing to install):

claude mcp add --transport http esos https://api.esos.ai/mcp \
  --header "Authorization: Bearer esos_pat_…"

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "esos": {
      "url": "https://api.esos.ai/mcp",
      "headers": {
        "Authorization": "Bearer esos_pat_…"
      }
    }
  }
}

Tools

create_robot
A robot from a sentence (and an optional template)
change_robot
“Add arms so it can wave”: the Studio assistant, saved as a new version
run_tests
The robot’s scripted test guests, run through the real interpreter
estimate_build
Cost per unit at a quantity, suggested price, margin, café payback
publish_robot
Publishes publicly, after the tests and checks pass (asks for confirm)
get_share_link
The public demo on your store
list_robots · get_robot
Your robots and their Robot Spec
list_units · fleet_summary · ask_fleet
The robots at your clients, live

Resources: esos://robots/{id}/spec and esos://robots/{id}/tests. A token can only reach its workspace, never admin pages, and stops working the moment you revoke it.