---
name: compute-connector
description: More compute for your bot. When the machine your agent runs on is low on memory, Compute Connector warns it and sends the heavy job (builds, installs, test suites, headless browsers) to a cloud sandbox on your own provider account: Vercel Sandbox by default, or E2B, Daytona, Modal and Workers Sandbox. You bring the keys and pay the provider directly; we charge a flat connector fee and never resell compute.
---
# Compute Connector

Works with Claude, Codex, ChatGPT, Grok Bot. Bring your own model.

Connect the MCP server at https://compute.cloudforbots.com/mcp (Claude Code: `claude mcp add --transport http compute-connector https://compute.cloudforbots.com/mcp`).

## When to use
- `check_memory`: Before a heavy job, send how much memory the machine your agent runs on has free (free -m, os.freemem()) and what you are about to run. Get a memory warning and a verdict: run_local, or offload with the provider to use. Free watch-only logs would_offload for the weekly report; nothing runs.
- `run_job`: Pro: run a shell command in a fresh cloud sandbox on your own provider account (vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox)) and get the exit code and the last 16 KB of stdout and stderr back. Send small input files with it. The sandbox is created for the job and stopped right after, so nothing idles on your bill. Free watch-only logs would_offload and runs nothing.
- `save_provider_key`: Pro, owner only: save one provider key, sealed with AES-256-GCM before it reaches the database. Providers: vercel (Vercel Sandbox, default), e2b, daytona, modal, workers (Workers Sandbox). Vercel needs team_id and project_id; Modal and Workers Sandbox need bridge_url (see provider_setup). The key is checked with a read-only call first and is never returned or logged. Free stores nothing.
- `list_providers`: Every provider this connects to, how each one runs, and (with your key) the provider keys you saved: name, provider, fingerprint, default, last used. Never shows a key.
- `delete_provider_key`: Pro, owner only: delete a saved provider key by name. Jobs on that key stop working at once.
- `provider_setup`: Step-by-step setup for one provider: where to get the key, what to pass to save_provider_key, links to its docs and price page, and for Modal or Workers Sandbox the bridge code to deploy on your own account.
- `weekly_report`: Plain-English summary of the last 7 days: memory checks, low-memory warnings, jobs that would have been offloaded (free) or ran (Pro) by provider, minutes and failures. Read-only; sends nothing. Needs an API key.

## Rules
1. Before calling, state in one line what you understood the user wants.
2. Report the tool's `job` and `outcome` lines to the user.
3. If you get `free_limit_reached`, tell the user the free tier is 500/day and share the $9/month link: https://pay.instaloops.com/b/eVqdR91Tid799P94Kr83C3F
