InstaBox MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@InstaBox MCPcreate a machine, open example.com in its desktop, and screenshot it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
instabox-mcp
A remote MCP server for InstaBox cloud machines, made for web clients (Claude.ai, ChatGPT) that can't run the InstaBox CLI. It speaks Streamable HTTP and has its own single-user OAuth login, so connecting a client is: paste the URL → enter your password → done.
Tools
Area | Tools |
Account |
|
Machines |
|
Lifecycle |
|
Commands & files |
|
Snapshots |
|
Public ports |
|
Desktop (computer use) |
|
Lifecycle tools wait up to ~45s (web clients time out around a minute) and otherwise return the
operation ID to follow with get_operation. Long commands should use run_command with
background: true, which logs to ~/.mcp-jobs/<job>.log in the machine.
Related MCP server: remote-access-mcp
Computer use
Machines have an optional Linux desktop (Xfce + Chromium). The model can see and drive it:
desktop_start: installs the desktop on first use (~30s, once) and starts it.desktop_actionwithopen_url,click,double_click,right_click,move,drag,scroll,typeorkey(e.g.ctrl+l). It returns a screenshot afterwards by default, so each step is one round trip.desktop_screenshotany time. Images are JPEG by default (format: "png"for sharp text).
desktop_stream_url gives you a live link to watch along in your own browser (view-only by
default). Input runs through xdotool on display :1, the same way the official SDK does it.
Configuration
Variable | Required | |
| yes | Public HTTPS URL, no trailing slash. MCP endpoint is |
| yes | From the InstaBox dashboard → API keys |
| yes | What you type on the login page |
| yes | ≥32 chars, |
| no | Default 3000 (Railway sets it) |
| no | Default 1h / 30d |
| no | Default 45 |
Deploy
Every push to main builds ghcr.io/<owner>/instabox-mcp:latest (amd64 + arm64) plus a
sha-xxxxxxx tag; a v1.2.3 git tag also publishes 1.2.3 and 1.2.
If the repo is private, the GHCR package is private too: either make the package public
(GitHub → Packages → instabox-mcp → Package settings) or give your host registry credentials.
Railway: New project → Deploy from GitHub repo (it builds the Dockerfile), or Docker image
ghcr.io/<owner>/instabox-mcp:latest. Add the env vars, generate a domain, set PUBLIC_URL to it,
health check path /healthz.
VPS: cp .env.example .env, fill it in, then DOMAIN=mcp.example.com docker compose up -d.
Caddy gets the HTTPS certificate automatically.
Connect a client
Claude.ai: Settings → Connectors → Add custom connector →
https://<your-domain>/mcp.ChatGPT: turn on developer mode, then add a custom connector with the same URL and OAuth auth.
Both pop up the login page; enter AUTH_PASSWORD.
Local development
npm install
cp .env.example .env # PUBLIC_URL=http://localhost:3000
npm run build && node --env-file=.env dist/index.jsTest with npx @modelcontextprotocol/inspector against http://localhost:3000/mcp.
Security notes
Anyone who logs in can run commands on your machines, so use a long password. The login form is rate limited (10 tries per 15 min per IP).
OAuth state is stateless (HMAC-signed with
TOKEN_SECRET), so redeploys never sign you out.Requires HTTPS in production; the OAuth library refuses a non-HTTPS issuer except on localhost.
This server cannot be deployed
Maintenance
Related MCP Connectors
Publish and manage HTML pages and multi-file static websites directly from Claude, ChatGPT, Cursor, Codex, and other AI agents via MCP. Streamable HTTP with OAuth 2.1 browser sign-in — no API key to copy.
Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Termalin's hosted MCP server. Claude, ChatGPT or any MCP client runs commands, moves files over SFTP, queries databases and reads server metrics and monitoring alerts on your servers, keylessly through Termalin Connectors: no SSH key is handed over and no inbound port is opened. Per-host command policy and an audit log. Needs a termal.in Pro or Team account (new accounts start with a 14-day Pro trial).
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA production-grade MCP server that lets AI cloud services control and manage your Linux server securely via HTTP/SSE.-
- AlicenseNot gradedqualityAmaintenanceTurns any Linux server into an AI-agent-accessible machine over HTTPS, allowing MCP clients like ChatGPT, Claude, and Grok to securely control files, run shell commands, inspect system state, query SQLite, and work with git behind a bearer token.124 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as ChatGPT and Claude to administer Linux or macOS hosts through authenticated Streamable HTTP, including running shell commands, reading and writing files within a workspace, listing directories, and retrieving system metrics.152 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP gateway that gives an AI client control of a real headed Chromium desktop and persistent workspace, with file, shell, process, and code-editing tools routed through a single control lease. Includes server-side read-only observation, server-enforced human takeover, and pause/stop controls so a person can watch, intervene, and hand control back.5Apache 2.0