Skip to main content
Rerun exposes two programmatic surfaces, and only two.

The MCP server

A single endpoint, POST https://app.rerun.build/api/mcp/account, that speaks the Model Context Protocol. It carries 45 tools covering agents, skills, scheduled tasks, webhook triggers, connectors, databases, runs and template authoring.

Webhook triggers

A public URL per trigger. Anything that can send an HTTP request can start an agent run, with no SDK and no key exchange.
The Rerun API is available on a paid plan. A free trial does not include it, so start your subscription before creating a key.

​
There is no REST API

Every capability is reached through the MCP endpoint. There is no /v1/agents, no OpenAPI document, and no other route that accepts an API key. If you are writing a plain HTTP client rather than plugging in an AI coding assistant, you still call the MCP endpoint: it is ordinary JSON-RPC 2.0 over POST, so curl works fine. See Protocol.

​
Who this is for

The API was designed for an AI coding assistant sitting next to you. You connect Claude Code, Codex or Cursor to your Rerun workspace, then describe what you want in plain language:
Create an agent that watches our support inbox, writes a daily summary into the shared database, and pings me on Slack when a refund request comes in.
The assistant calls create_agent, upsert_skill, upsert_schedule, attach_connector and send_message to build and test it. See Connect a client. Everything the API does is also available in the Rerun app. The API exists so you can script it, version it, and repeat it.

​
What a key reaches

An API key is scoped to one workspace and nothing finer. It reaches every Box, every agent, every database and every run of that workspace, with full read and write. Treat it as a production credential.

​
Tool index

Agents

list_spaces list_agents get_agent create_agent update_agent delete_agent

Skills

list_skills get_skill upsert_skill delete_skill

Scheduled tasks

list_schedules upsert_schedule run_schedule_now delete_schedule

Triggers

list_triggers upsert_trigger test_trigger rotate_trigger_token delete_trigger

Messages and runs

send_message list_runs get_run

Databases

list_tables db_query db_execute list_space_tables space_db_query space_db_execute

Connectors

search_connectors list_connectors list_agent_connectors attach_connector detach_connector

Templates

12 authoring tools, reserved for expert sandbox accounts

​
What the API cannot do

Some things are deliberately left to the app, mostly because they involve a secret or a decision that should not be automated. See Limits and guarantees for the full list. The short version:
  • No credential ever goes through the API. attach_connector declares a connector, and the account owner finishes the sign-in in the app.
  • No billing, no plan change, no member management, no Box creation.
  • No API key management. You cannot mint or revoke a key over MCP.
  • No template publication. You submit a draft, the Rerun team publishes it.

​
Next steps

Create a key

Connect a client

Read the protocol