MCP Server

The Runta MCP server lets an AI assistant operate your Runta runtimes. The assistant uses your Runta account and your organization role.

https://mcp.runta.com/mcp

The server uses Streamable HTTP and OAuth sign-in.

Install

Client	Link
Claude	Runta connector
ChatGPT	Runta plugin

Connect a Client

Make sure that you have a Runta account in an organization. To get an account, go to dashboard.runta.com.

When you connect, Runta shows a consent page in your browser. Make sure that the client name and the return host are correct. Select the organization, then approve. Do not paste a password or token into the conversation.

Claude

1. Open the Runta connector.
2. Select Connect.
3. Sign in to Runta and approve the organization.

To add the server manually, go to Customize → Connectors. Select Add custom connector and enter the server URL.

Claude Code

claude mcp add --transport http runta https://mcp.runta.com/mcp

Start Claude Code and type /mcp. Select runta, then select authenticate.

ChatGPT

1. Open the Runta plugin.
2. Add Runta.
3. Sign in to Runta and approve the organization.

Cursor

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

{
  "mcpServers": {
    "runta": {
      "url": "https://mcp.runta.com/mcp",
      "auth": {
        "CLIENT_ID": "https://api.runta.com/oauth/clients/cursor",
        "scopes": ["runtime:read", "runtime:manage"]
      }
    }
  }
}

Open the MCP settings in Cursor and connect runta.

Other clients

A client that supports OAuth Client ID Metadata Documents needs only the server URL.

A client without browser sign-in can send a Runta token:

Authorization: Bearer rt...

Use the token that runta login stores for the Runta CLI. Do not use a dashboard API key. The server refuses API keys. Keep the token secret.

To disconnect, remove Runta in the client.

Permissions

Scope	Allows
runtime:read	Read runtimes, ports, egress, checkpoints, images, desktops, and SSH keys
runtime:manage	Create, change, and delete these items, and run commands in a runtime

The server sends each tool call to the Runta API with your credential. The API applies the same role checks as the dashboard and the CLI. To change a runtime that another user owns, you need the Owner or Admin role. See Team Access and Roles.

Each tool tells the client if it reads, changes, or deletes data. The client can ask you before it runs a tool that changes or deletes data.

Tools

Area	Tools
Account	whoami
Runtimes	list_runtimes, get_runtime, create_runtime, start_runtime, stop_runtime, pause_runtime, resume_runtime, resize_runtime, set_idle_policy, delete_runtime
Commands	run_command
Published ports	list_ports, publish_port, unpublish_port
Egress	get_egress, set_egress_policy, set_token_saving
Checkpoints	list_checkpoints, create_checkpoint, restore_checkpoint, delete_checkpoint
Runtime Images	list_runtime_images, build_runtime_image, list_runtime_image_builds, cancel_runtime_image_build, delete_runtime_image
VNC desktop	get_vnc, enable_vnc, disable_vnc, list_vnc_credentials, create_vnc_credential, revoke_vnc_credential
SSH access	list_ssh_keys, list_runtime_ssh_keys, attach_ssh_key, detach_ssh_key

Lifecycle tools return when Runta accepts the request. The assistant then reads the status with get_runtime, list_checkpoints, or list_runtime_image_builds.

Example Prompts

• “List my Runta runtimes and their status.”
• “Create a runtime named demo and tell me when it is running.”
• “Publish port 3000 on demo and give me the URL.”

Limits

• run_command runs one command and returns its output. It cannot answer prompts. For an interactive shell, use runta exec or SSH.
• The server cannot copy files from your computer. Use runta cp.
• build_runtime_image cannot COPY local files into the image.
• The server does not manage secrets, billing, API keys, or organization members.
• All users with the URL of a published port can access the service on that port.

Data and Privacy

The server sends tool arguments to the Runta API and returns the result to the client. The server does not read your conversation and does not store tool arguments or results. See the Privacy Policy and the Terms of Use.

Troubleshooting

Problem	Action
Runta does not accept the connection	Your sign-in expired. Connect Runta again.
A tool reports permission denied	Your role cannot do this change. Ask an organization admin.
The consent page shows Unverified	Approve only if you started the connection and you know the return host.
The client reports MCP is temporarily disabled	Wait some minutes, then try again.
The server refuses a bearer token	Use the token from runta login, not a dashboard API key.

For help, send an email to support@runta.com. Include the client name, the time of the problem, and the error message.