Linux desktops

A Maritime Linux desktop is a persistent computer (XFCE, Chromium, LibreOffice) for each of your end users, driven by your model. You connect the Maritime MCP server to whatever agent you already run; the model calls get_computer once per end user and then computer in a screenshot, act, verify loop. Maritime creates the desktop, keeps it warm, sleeps it when idle, wakes it on the next action, and keeps its files and logins between sessions. There is no lifecycle for you to manage.

At a glance

What it is

A persistent Linux desktop (XFCE, Chromium, LibreOffice) per end user, which your model drives over MCP or REST.

Use it for

Websites and apps with no API, browser logins, work a person can take over by link.

Use something else when

• No screen needed: Agent box
• Windows-only software: Windows desktop
• A mobile app: Android phone

Start it

POST /api/v1/computers with externalUserId, get_computer over MCP, or New sandbox (?type=computers).

Lifecycle

Sleeps after 5 idle minutes with its memory saved and wakes in about a second. The memory snapshot is kept 7 days; the disk until you delete the computer.

Price

$0.12 an hour awake, per second, for 2 vCPU and 4 GB with the desktop, streaming and takeover. Asleep: $0.08 per GB-month of disk.

Limits

• 1200 x 750 model screenshots
• 50 actions per batch
• run_shell 30 seconds
• 8 MiB per file read or write.

In sixty seconds

1. Use the key you already have. A manage or full-access Maritime key drives computers and agents alike, so the MCP server takes the same bearer token as the rest of the API. To hand out a key that reaches computers and nothing else, create a Computers key in the Computers section of Settings, API keys: a key whose only scope is computers is refused on every other Maritime endpoint. Dashboard sessions cannot reach /api/v1/computers; that surface takes an API key.
2. Add the MCP server to your agent with one of the snippets below.
3. Your model calls get_computer with the end user's id, gets a computer_id, then drives it with computer. The first call creates the desktop; every later call for the same end user returns the same one.

Connect your model

The server speaks Streamable HTTP and authenticates with your Computers key as a bearer token. Replace mk_... with the key; the exact endpoint for your deployment is shown on the Computers page.

Copy MCP config

{
  "mcpServers": {
    "maritime-computers": {
      "type": "http",
      "url": "https://mcp.maritime.sh/mcp",
      "headers": {
        "Authorization": "Bearer mk_..."
      }
    }
  }
}

Tool timeouts

Most MCP clients cut a tool call off after 60 seconds. Two calls here can pass that, and both need the limit raised, not just the takeover:

• get_computer on first use creates the desktop: 3 to 8 seconds normally, up to 60 on a cold placement. Later wakes take about 3 seconds.
• request_takeover with wait: true holds until the person clicks Done or Failed, which is minutes. Leaving wait at its default returns at once and needs no extra time.

Tools

Billing

A computer is billed per second while it is awake, at $0.12 an hour, with no minimum. Asleep, it is billed only for its disk, $0.08 per GB-month. Nothing is counted per action or per session. Windows desktops are $0.18 an hour and Android phones $0.15 an hour, on the same terms.

The Computers page lists your computers. The Billing page is where the plan is started, changed and cancelled, once, for the whole account.

Limits

Errors