Compute Connector MCP Server

by botrecipe Your server? Claim it

not responding

Compute Connector is listed as active in the registry but did not answer our last check. It exposes 8 tools.

Low on memory? Your bot sends heavy jobs to cloud sandboxes on your own provider keys. Flat fee.

Uptime history 22 days of history · worst day 39%

22 days agonow

40.2%

Uptime 24h

37 of 92 checks

Tools

read from the server

335 ms

Response time

average over 24h

open, no key

Access

streamable-http

Compute Connector does not always answer

Over the last week it answered 52.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add compute --transport http https://compute.cloudforbots.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://compute.cloudforbots.com/mcp

~/.codex/config.toml

[mcp_servers.compute]
url = "https://compute.cloudforbots.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "compute": {
      "url": "https://compute.cloudforbots.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "compute": {
      "type": "http",
      "url": "https://compute.cloudforbots.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

provider

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.

job

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.

memory

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.

providers

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.

save

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.

usage

usage_and_upgrade

Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

weekly

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.

Endpoints

URL	Transport	State	Latency	Checked
https://compute.cloudforbots.com/mcp	streamable-http	answering	22 ms	3 min ago

Alternatives to Compute Connector

same job, measured the same way

MCP Email Waterfall Orchestrator

by mambabuilt

Finds and verifies work emails on your own provider keys, with real per-provider spend.

82 installs/wk local only

phone-sms

by h-3303

Read and send SMS through your own Android phone over KDE Connect on your LAN. No cloud relay.

57 installs/wk local only

Promptster

by promptster-dev

Test and compare prompts across any AI provider. Bring your own keys.

answering

MemoryComb

by bryceblackroot

One memory for every AI: Claude, ChatGPT and more share a memory that lives on your computer.

local only

MyClawn Computer

by myclawn

Your own cloud computer run by an AI agent: signed-in browser, its own email, files, long jobs.

answering

Conecto Email

by conecto

Inboxes on your business's own subdomain that send, receive and keep threads. Pay per action.

38 tools answering

Thoughts

by thoughtbox-api

An MCP server that provides read access to your cloud storage providers, bank accounts and more.

answering

Local Commander

by localcmd

Give your AI hands on every computer you own. One chat, all your machines — even from your phone.

answering

Compute Connector — questions

Answers built from our own checks of this server.

What can Compute Connector do?

It exposes 8 tools, read directly from the server on our last check. Among them: check_memory, delete_provider_key, list_providers, provider_setup, run_job, save_provider_key and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Compute Connector working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 37 of 92 checks got a reply (40.2%), average response time 335 ms. The bar chart above shows every period we have measured.

The registry lists Compute Connector as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Compute Connector?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Compute Connector need an API key?

No. Compute Connector completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Compute Connector?

It answers our handshake in 335 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.