Documentation
Sprawl runs your operations for you — each its own project, each with its own fleet of agents. Everything here describes how Sprawl actually behaves today — no aspirational docs.
Getting started
From zero to a running operation: start from what you’ve built (or describe it), approve one blueprint, activate the fleet, and put it on autopilot.
Connecting your accounts
Give your agents access to your tools — scoped per operation (a different Gmail, Slack, or X each), granted through each service’s own sign-in, and reversible anytime. 100+ integrations.
How automations run
The ways your agents run work on their own — on a schedule, on an event trigger, as a goal-directed pursuit that paces itself, or on demand. All in the background, all under the same approvals.
How approvals work
Agents act on your real accounts — approvals keep you in control. Routine work runs on its own; anything reaching the outside world waits in your inbox with a preview you can edit before you approve; the riskiest actions never run autonomously.
MCP server — for AI agents
Connect any MCP-capable AI agent (Claude, Cursor, and others) to Sprawl: one HTTP endpoint for tasks, scheduling, memory, and 100+ integrations.
Questions the docs don't answer yet? The fastest way to get help is to start a free account and ask Sprawl directly in the app. Also see the FAQ.