Developers

Agent servers with sandbox-grade isolation

Persistent Linux servers for AI agents. Run code, manage files, use the terminal, and ship to public URLs. Connect over MCP in one config line, or delegate end-to-end with prompt().

Start for free View docs

Coding agentsBackground automationsDeep researchData analysisMCP tool serversDeployed apps

srv_2k9 · running

LIVE

exec()

Tier

medium

Workspace

12.4 / 20 GB

Projects

4 / 10

execread_filewrite_filepromptdeploy

How it works

From MCP config to live URL in four steps

Same mental model as sandbox SDKs: connect, provision, run code, extract results. We add persistence, templates, and optional staffed delivery.

Tool surface

exec()write_file()prompt()deploy()

01

MCP host

Cursor · ChatGPT · your loop

02

Server

Isolated Linux + volume

03

Projects

Workspaces + git

04Live

Public URL

*.apps.server4agent.com

01

Connect your agent

Add one MCP config entry or call the REST API with a scoped API key. Works with Cursor, ChatGPT, LangChain, or any tool-calling loop.

02

Provision a server

Create an isolated Linux server sized for your workload. Add projects from a template or start blank. Secrets inject as env vars.

03

Run work in the sandbox

Drive exec, read_file, and write_file yourself, or hand off with prompt(). Install packages, use git, run tests, iterate until done.

04

Ship or extract results

Deploy to a public URL, pull stdout and artifacts, or subscribe to webhooks. Persistent projects resume where the last session left off.

Use cases

Built for AI agents, MCP hosts, and agentic workflows

The same categories teams run on sandbox infrastructure, plus a staffed build agent when you want a finished URL back.

Coding agents

Your agent drives the primitives directly: provision a server, write code, run commands, iterate on errors, deploy when ready. Same surface as a sandbox SDK, exposed as MCP tools.

execwrite_fileread_filedeploy

Building blocks

Sandbox primitives + staffed delivery

Learn five concepts and you understand the whole surface.

Server

Isolated Linux compute. Sized small, medium, or large. Persistent volume, scale-to-zero idle, wake on demand.

Project

Workspace per app or job. Public or private URL, persistent or ephemeral lifecycle, git-backed files.

Sandbox primitives

exec, read_file, write_file, list_files. Install packages, use the terminal, run any stack your agent needs.

Template

Starter catalog via list_templates. Pre-fills visibility, lifecycle, and description for landing pages, APIs, monitors, and automations.

prompt()

Optional staffed path. Send a goal; the build agent plans, writes, runs, and ships without your loop driving every step.

Templates

Starter projects, not blank slates every time

Like custom sandbox images, but opinionated for real deliverables: landing pages, APIs, monitors, and standing automations.

Landing page

Public site at a live URL

persistent · public

REST API

A JSON API server

persistent · private

Data pipeline

One-shot ETL or processing job

ephemeral · private

Web scraper

One-shot scraping task

ephemeral · private

Dashboard

Live admin or analytics view

persistent · public

Invoice processor

Read invoices, push to your books

persistent · private

CRM sync

Enrich + dedupe leads into your CRM

persistent · private

Report digest

Scheduled report, pulled and emailed

persistent · private

Flight price watcher

Track fares, alert on price drops

persistent · private

Job tracker

Watch listings, ping on new matches

persistent · private

Price drop monitor

Watch products, ping when they fall

persistent · private

One server hosts many projects. Templates pre-fill visibility, lifecycle, and description via list_templates.

Template reference

Get started

Write files, run code, ship a URL

Your agent writes real source files, installs dependencies, and runs them — over MCP, REST, or its own tool-calling loop. No Server4Agent SDK required on the outer side.

CursorChatGPTLangChainLangGraphAny MCP hostRaw HTTP

Diagram: MCP host connects to an isolated server and deploys to a public URL

Need help? Read the quickstart, browse examples, or email hello@server4agent.com.

MCP: https://mcp.server4agent.com
REST: https://api.server4agent.com

mcp.config.json

{
  "mcpServers": {
    "server4agent": {
      "url": "https://mcp.server4agent.com",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Features

Features your agents will love

Real-world tools for agentic workflows: isolation, persistence, shell access, and a path to production URLs.

Works with any MCP host

Cursor, ChatGPT connectors, LangChain, LangGraph, or your own tool-calling loop. One JSON config entry.

Persistent, not per-call

Servers keep workspace state between tasks. Pick up where the last session left off instead of cold-starting every run.

Run anything on Linux

Python, Node, Go, Rust, shell scripts, cron. If it runs in a container, your agent can run it here.

Secure & isolated

Each server is tenant-scoped. Agent-generated code runs in sandboxed compute with secrets injected as env vars.

Long-running work

Persistent projects for monitors and bots. Ephemeral projects for one-shot pipelines you clean up when done.

Ship to a public URL

Deploy to *.apps.server4agent.com with managed TLS. The deliverable is an addressable app, not just stdout.

Illustration of tenant-scoped server isolation with nested project workspaces

Isometric illustration of a server hosting multiple sandbox projects with a public deploy target

Use terminal

exec any command

Git history

per-project commits

Spend caps

per API key

MCP tools

Full tool surface

Sandbox-style primitives and higher-level build tools on one server.

Lifecycle

create_server
list_servers
get_server
update_server
control_server
delete_server

Projects

list_templates
create_project
list_projects
get_project
update_project
cleanup_project
delete_project

Build

prompt
start_build
get_build
deploy

Primitives

exec
list_files
read_file
write_file
delete_file

MCP reference REST API Webhooks llms-full.txt

Cookbook

Get inspired by our examples

Production-shaped patterns for MCP hosts, REST clients, and autonomous agents. Filter by language or integration style.

Language / host

Pattern

32 examples

Connect Cursor over MCP

New

Example · Docs

Full agent loop in Python

Example · Docs

Generic tool-calling loop in TypeScript

Example · Docs

LangChain + MCP tools

Example · Docs

LangGraph + MCP tools

Example · Docs

ChatGPT MCP connector setup

Example · Docs

Hand off a goal with prompt()

Example · Docs

Slack revenue bot via prompt()

Example · Docs

Write and run a Python function

Example · Docs

Write and run code in TypeScript

Example · Docs

Run a data script with exec

Example · Docs

Build and deploy a Next.js app

Example · Docs

All docs examples Browse showcase

Compare

Sandbox SDK vs staffed agent servers

We cover the same ground as ephemeral sandboxes, then add persistence, MCP-native tools, and optional full delivery via prompt().

Sandbox SDK

Server4Agent

Core unit

Ephemeral VM per call

Persistent server + projects

Code execution

runCode / exec in your SDK

exec MCP tool + full shell

Typical output

stdout, files, charts in memory

stdout + optional live public URL

Who ships the app

Your agent orchestrates

Your agent or our build agent via prompt()

Integration

Language SDK

MCP + REST + webhooks

Spend control

Per invocation metering

Per-key cap on owner account

Starter environments

Custom sandbox templates (Docker)

list_templates catalog (12 starters)

State between runs

Pause and resume sandboxes

Persistent servers + project git history

Git workflow

Clone repos, push from sandbox

Per-project commits in the dashboard

Delivery signals

SDK polling for run status

10 webhook events (build, deploy, spend)

Many teams use a sandbox for quick code execution and Server4Agent when the deliverable is a deployed app, a standing automation, or a project engineers will take over. See the manager-facing story.

Documentation

Quickstart, MCP tools, REST API, webhooks, and worked examples.

Browse docs

API reference

Provision servers, run tasks, manage files, deploy, subscribe to events.

View API

LLM context

Machine-readable product summary for assistants and codegen tools.

llms-full.txt

Get started today

Persistent agent servers with real-world tools. Connect over MCP and ship your first public URL.

Sandbox primitives: exec, files, shell, deploy
Staffed path: prompt() for end-to-end delivery
Per-key spend cap your agent cannot override

Start for free View docs

Agent servers with sandbox-grade isolation

From MCP config to live URL in four steps

MCP host

Server

Projects

Public URL

Connect your agent

Provision a server

Run work in the sandbox

Ship or extract results

Built for AI agents, MCP hosts, and agentic workflows

Coding agents

Agent delegation

Deep research agents

Data analysis & viz

Background automations

Vibe coding & apps

Secure MCP servers

Public deploy surface

Sandbox primitives + staffed delivery

Server

Project

Sandbox primitives

Template

prompt()

Starter projects, not blank slates every time

Landing page

REST API

Data pipeline

Web scraper

Dashboard

Invoice processor

CRM sync

Report digest

Flight price watcher

Job tracker

Price drop monitor

Write files, run code, ship a URL

Features your agents will love

Works with any MCP host

Persistent, not per-call

Run anything on Linux

Secure & isolated

Long-running work

Ship to a public URL

Full tool surface

Lifecycle

Projects

Build

Primitives

Get inspired by our examples

Connect Cursor over MCP

Full agent loop in Python

Generic tool-calling loop in TypeScript

LangChain + MCP tools

LangGraph + MCP tools

ChatGPT MCP connector setup

Hand off a goal with prompt()

Slack revenue bot via prompt()

Write and run a Python function

Write and run code in TypeScript

Run a data script with exec

Build and deploy a Next.js app

Sandbox SDK vs staffed agent servers

Documentation

API reference

LLM context

Get started today