Sprawl
Stand up an operation from Cursor/Claude Code: a fleet of agents, each on its own model and connected account, running on a schedule after your session ends. MCP: https://sprawl.to/api/mcp
Documentation
Connect an agent to Sprawl
Your agent already writes code and runs on a schedule. What it can't do is keep a fleet running on your accounts after the session ends. Point it at Sprawl over MCP and it designs the operation; Sprawl runs it — each agent on its own model, on its own connected account, on its own schedule.
What you can do
- Design an operation — survey the user's repos and stack, then propose a complete blueprint: agents, their skills, their schedules and the accounts each one needs. Nothing is created until a human approves it.
- Pick a model per agent — a cheap one for the hourly sweep, a stronger one for the weekly analysis, inside a single operation. Independent of whichever model is doing the designing.
- Give each agent its own account — Sprawl holds multiple accounts per provider, scoped per operation: a work Gmail on one, a personal one on another; two X handles; two Slack workspaces.
- Stand it up, then check on it — provision the whole fleet atomically, and read back what ran and what it cost without leaving your editor.
Connect
The server is an HTTP MCP endpoint that speaks JSON-RPC 2.0 over POST:
https://sprawl.to/api/mcp
Authenticate with a bearer API key. Create one (free read-only keys are available) in account settings once you've created a free account, then pass it as Authorization: Bearer sprawl_sk_…
Quickstart
List the available tools to confirm your key works:
curl -s https://sprawl.to/api/mcp \
-H "Authorization: Bearer sprawl_sk_..." \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Add to an MCP client
Most MCP clients accept an HTTP server config like this:
{
"mcpServers": {
"sprawl": {
"type": "http",
"url": "https://sprawl.to/api/mcp",
"headers": { "Authorization": "Bearer sprawl_sk_..." }
}
}
}
A machine-readable descriptor (tools, auth, and pricing) is served without auth at /.well-known/mcp/server-card.json.
Pricing & metering
There is no subscription. Every account starts with $3 of usage, each run draws its own price from that balance, and you add more whenever you want — from $5, never expiring.
When an agent runs low, sprawl_get_usage returns the remaining balance in dollars, what has been spent this month, and the billing page to add more. Adding balance is the account owner's action — an agent can surface the link, and cannot charge a card.
Agentic checkout (ACP)
Sprawl also exposes Agentic Commerce Protocol checkout endpoints (the open standard by OpenAI & Stripe) for adding balance, so an agent can run a standards-based checkout itself.
- Public product feed:
GET /api/acp/feed - Create, re-price, retrieve, or cancel a session:
/api/acp/checkout_sessions(bearersprawl_sk_auth)
Payment completion via Shared Payment Token is not yet enabled. Until it is, a session can be created and priced but not paid — the account owner adds balance from the billing page above.
Get an API key
Create a free account, generate a key in settings, and point your agent at Sprawl in minutes.