( Docs )

Connect a coding agent (MCP)

Suprlative is an MCP server. Claude Code, Cursor or any MCP client can look up your fleet's issues, incidents, the telemetry around an incident, logs, firmware and software rollouts and the savings ledger while you work on robot code. It can also test a detector pattern on every past recording.

Every tool only reads. Nothing an agent does through MCP changes your data.

Claude CodeCursorAny MCP client

1. 01

   Get your command

   Sign in to Suprlative and open Account. Under API tokens, create a token and name it after the machine or tool, like "Claude Code on my laptop".

   The page shows the token once, with a ready-made command for Claude Code that has your Suprlative address and the token filled in. Copy both. The token isn't shown again.

2. 02

   Claude Code

   Paste the command from the Account page into a terminal. It has this shape:

   claude mcp add --transport http suprlative https://<your-suprlative-address>/mcp --header "Authorization: Bearer <your-token>"

   Copy

   You don't need to fill in the placeholders yourself: the Account page puts in your address and token.

3. 03

   Cursor, or any client that takes JSON config

   Add a server named suprlative to the client's MCP config, with the same two values from the Account page:

   {
     "mcpServers": {
       "suprlative": {
         "type": "http",
         "url": "https://<your-suprlative-address>/mcp",
         "headers": {
           "Authorization": "Bearer <your-token>"
         }
       }
     }
   }

   Copy
4. 04

   Self-hosted, on the same machine as the data

   Run the server over stdio instead of HTTP. No token is needed: it reads the data on that machine.

   claude mcp add suprlative -- <path-to-python> -m suprlative mcp

   Copy

   Use the Python that Suprlative is installed in. On its own, python -m suprlative mcp starts the server.

5. 05

   Try it

   Ask your agent things like:

   • "Using suprlative, what's the costliest recurring issue at <site> and which robots does it hit?"
   • "Did firmware 2.3.2 fix anything, and is it safe to roll out to the rest of the fleet?"
   • "Before I merge this fix, check how often 'battery low' log lines came with a stop at the dock in past recordings."

   The agent cites incident IDs (like INC-0042) and issue keys, so you can open each one in Suprlative.

6. 06

   Access and privacy

   • A token sees exactly the sites its owner can see: the sites in their workspaces.
   • Revoke a token any time on the Account page. Anything using it stops working.
   • Sites with AI switched off in their privacy settings aren't shared over MCP.

Tools

Each tool takes a site, except list_sites. When there is only one site, the site can be left out.

list_sites

The sites this token can see, with robots, incidents, issues and when each was last analysed.

fleet_summary

A site at a glance: robots with their firmware and software, robot-hours analysed, incident and issue counts.

list_issues

Every issue, ranked by impact, with its likely root cause, incident count, robots, zone and annual cost.

get_issue

One issue in full: root cause, evidence, recommended fix and how to verify it.

find_incidents

Filter incidents and list them, or count them with group_by to answer "which robot, zone or firmware?".

get_incident

One incident in full: robot, time, place, downtime, the signals that fired and the log lines around it.

telemetry_around

Telemetry from a few seconds before an incident to just after it, summarised per channel.

search_logs

Search the robots' log lines by text or regular expression.

list_rollouts

Firmware and software versions robots moved to, and what each update changed for every affected issue.

savings_ledger

What verified fixes have saved, fix by fix, in your costs or robot-hours.

list_detectors

The site's own detectors and how often each one matched.

test_detector

Run a detector rule over every past recording without saving it, and see where it matches.