MCP Server

1. Connect Claude Code with your browser

No token to create or paste. In a terminal with Claude Code installed, add the server once:

claude mcp add --transport http serversareup https://serversareup.com/api/mcp/v1

Then run /mcp inside Claude Code, choose serversareup and approve the connection in your browser. You choose what the assistant may do: looking is ticked, running commands and editing files are yours to tick, and spending money, creating API keys and changing team membership are never offered to an assistant. Access is renewed quietly while it is in use and lapses after 30 days without use. Disconnect an assistant at any time in Account > API Keys; its next call is refused.

2. Or connect with an API token

For scripts, CI and clients without browser sign-in. Generate a personal access token in Account > API Keys. Grant instances:read for access details, instances:exec for guest commands, SSH key leases and explicit credential retrieval, and instances:power for power actions. Purchasing requires both billing:write and instances:write; polling orders requires billing:read. File tools require instances:files:read or instances:files:write.

The assistant is only offered the tools your token allows: a read-only token never sees a tool that changes anything. Start narrow and add scopes when you need them.

Then point your client at the hosted endpoint, replacing the token. In Claude Code:

claude mcp add --transport http serversareup https://serversareup.com/api/mcp/v1 \
  --header "Authorization: Bearer sau_your_token_here"

Cursor and other clients that support remote MCP servers take the same endpoint in their configuration. Cursor uses .cursor/mcp.json for project settings.

{
  "mcpServers": {
    "serversareup": {
      "url": "https://serversareup.com/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer sau_your_token_here"
      }
    }
  }
}

Keep the token out of committed project configuration. Revoke it in Account > API Keys and the next call is refused.

3. Or run the local package

For clients that only launch local servers. Requires Node.js 20 or later. The download comes directly from Servers Are Up.

npm install -g https://serversareup.com/downloads/serversareup-mcp-server.tgz

Add it to your assistant's MCP configuration, replacing the token.

{
  "mcpServers": {
    "serversareup": {
      "command": "serversareup-mcp",
      "env": {
        "SAU_API_TOKEN": "sau_your_token_here"
      }
    }
  }
}

The process runs locally with your token. Its tools are named differently from the hosted ones (for example get_catalog and exec_instance); ask your assistant to list them.

4. Purchase and configure a service

1. Use sau_search_catalog to choose a product and review its configuration and current legal terms.
2. Authorize the purchase and terms. Use sau_create_order with one item, the accepted legal document versions and hashes, and a stable idempotency_key. Reuse that key for retries and confirmation.
3. If the response requires confirmation, review the price before resubmitting with confirm: true. If it returns checkoutUrl, complete the secure payment page.
4. Poll sau_get_order until provisioning finishes, then use sau_get_instance_access for the published SSH, RDP, app, or web console details.
5. Use sau_exec_instance, sau_read_instance_file, and sau_write_instance_file to configure guests that support shell access. Explicit credential retrieval records an audit event.

Plan capacity and sufficient credits can fund eligible orders through the API. Card checkout may require your interaction. Organization tokens stay within their organization. See the order request contract for payloads and error codes.

5. SSH from your own terminal

For work that needs a real shell, lease SSH access to a running Linux server with your own key. You send only the public half; we never see the private key and never hand out the server's password. A lease lasts from one minute to one hour, and the server itself stops accepting the key when it ends, with nothing left to clean up. Keys you added yourself are never touched.

Ask your assistant to "open SSH to my server for 30 minutes": it generates a key, calls sau_ssh_authorize, pins the host key from the reply and connects. sau_ssh_revoke ends a lease early. The same thing over the REST API:

# 1. A throwaway key pair. The private half never leaves your machine.
ssh-keygen -t ed25519 -N "" -C sau-lease -f ~/.ssh/sau-lease

# 2. Ask for 30 minutes of access with the PUBLIC half, and keep the reply.
curl -s -X POST https://serversareup.com/api/v1/instances/INSTANCE_ID/ssh-leases \
  -H "Authorization: Bearer $SAU_API_TOKEN" -H "Content-Type: application/json" \
  -d "{\"publicKey\": \"$(cat ~/.ssh/sau-lease.pub)\", \"leaseSeconds\": 1800}" > lease.json

# 3. Pin the server's host key from the reply, then connect.
jq -r .knownHosts lease.json >> ~/.ssh/known_hosts
ssh -i ~/.ssh/sau-lease -p "$(jq -r .ssh.port lease.json)" \
  "$(jq -r .ssh.username lease.json)@$(jq -r .ssh.host lease.json)"

Requires instances:exec. Up to 16 live keys per server; every grant and revoke is recorded in your activity log. Revoking does not close a session that is already open. Game servers lease keys through their control endpoint instead.

6. API Versioning, Deprecation & Sunset Policy + CLI

All MCP tools dispatch to our versioned Public REST API (/api/v1) and the Streamable HTTP MCP endpoint (/api/mcp/v1). Every response includes X-API-Version: v1 and IETF RateLimit-* headers. Breaking changes are introduced only under a new major path version (/api/v2), and any deprecated version or operation remains active for a minimum 6-month deprecation notice window while emitting RFC 8594 Deprecation and Sunset HTTP headers. See the API Versioning & Deprecation Policy and API docs.

Prefer terminal scripting? Install the official sau CLI package directly from Servers Are Up: npm install -g https://serversareup.com/downloads/serversareup-cli.tgz.