MCP server

The Runtime MCP server lets an AI client create, run and govern your Runtime agents from chat. It calls the same API as the dashboard and the Agent CLI, with the same scopes, roles and rate limits.

https://mcp.runtm.com/mcp

Streamable HTTP. Sign in with OAuth (your Runtime login, including SSO) or send a Runtime API key as a bearer token. See Authentication.

Quick start

Pick your client. The first time you use it, it opens a browser to sign in to Runtime.

claude mcp add --transport http runtime https://mcp.runtm.com/mcp

Then run /mcp in Claude Code, pick runtime and sign in.

Open Settings → Connectors and click Add custom connector.
Name it Runtime, paste https://mcp.runtm.com/mcp and click Add.
Click Connect and sign in to Runtime.

Claude Desktop uses the same connectors as Claude.ai. On Team and Enterprise plans, an owner may need to add the connector first.

Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
Click Create, name it Runtime, paste https://mcp.runtm.com/mcp and choose OAuth.
Sign in to Runtime when ChatGPT asks.

Send your bot: Add a custom MCP server called runtime at https://mcp.runtm.com/mcp.
Check the name and URL it shows, then confirm.
Click Authorize on the connect card and sign in to Runtime.

Grok Bot connects custom servers with OAuth only, so it always uses sign-in, never an API key.

Add this to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "runtime": {
      "url": "https://mcp.runtm.com/mcp"
    }
  }
}

Open Cursor Settings → MCP and click Connect next to runtime.

Add this to .vscode/mcp.json:

{
  "servers": {
    "runtime": {
      "type": "http",
      "url": "https://mcp.runtm.com/mcp"
    }
  }
}

Click Start above the server entry and sign in when VS Code asks.

codex mcp add runtime --url https://mcp.runtm.com/mcp
codex mcp login runtime

Check it works: ask your client to call runtm_whoami. It returns your user, organization, role and scopes.

Use an API key instead

For clients without OAuth, MCP gateways and CI, send a Runtime API key as a bearer token. The key’s scopes decide what the client can do.

claude mcp add --transport http runtime https://mcp.runtm.com/mcp \
  --header "Authorization: Bearer $RUNTM_API_KEY"

{
  "mcpServers": {
    "runtime": {
      "url": "https://mcp.runtm.com/mcp",
      "headers": { "Authorization": "Bearer ${env:RUNTM_API_KEY}" }
    }
  }
}

{
  "inputs": [
    { "type": "promptString", "id": "runtm-api-key", "description": "Runtime API key", "password": true }
  ],
  "servers": {
    "runtime": {
      "type": "http",
      "url": "https://mcp.runtm.com/mcp",
      "headers": { "Authorization": "Bearer ${input:runtm-api-key}" }
    }
  }
}

# ~/.codex/config.toml
[mcp_servers.runtime]
url = "https://mcp.runtm.com/mcp"
bearer_token_env_var = "RUNTM_API_KEY"

Never paste an API key into a chat. Keep it in the client’s config or an environment variable.

What it can do

Area	Examples
Agents	List the roster and its triggers, create or update an agent, read the scorecard
Sessions	Launch a session, send a prompt, follow its events, resolve an approval, run a command
Context	Read a template, save a runbook skill, attach skills and MCP servers, rebuild
Guardrails	List and save allow, ask and deny rules, hooks and network rules
Triggers	Create Slack, GitHub, Linear and Email triggers and schedules, run a schedule once
Everything else	Search, describe and call any documented API operation

31 tools load by default. Add or drop groups with ?toolsets=. See Tools.

Safe by design

Your permissions, no more. Every call runs through the REST API with your scopes, org role and rate limits. Tools you can’t use are hidden.
No credentials in chat. A step that needs a key, token or password returns a dashboard link for you to finish. A request field named like a credential is refused.
Sandbox output is data. Session events, command output and files are labelled untrusted, and the model is told not to follow instructions in them.
A 403 is final. The model is told to name the missing permission, not to look for another way in.

Authentication

OAuth, workspaces, scopes and API keys.

Tools

Every tool, its inputs and toolsets.

Okta

Troubleshooting

Fix sign-in, 401, 403 and missing tools.

Get Started

Runtime MCP server

Build an agent

Platform reference

Quick start

Use an API key instead

What it can do

Safe by design

Next

Authentication

Tools

Okta

Troubleshooting

​Quick start

​Use an API key instead

​What it can do

​Safe by design

​Next

Authentication

Tools

Okta

Troubleshooting

Quick start

Use an API key instead

What it can do

Safe by design

Next