Sprawl
to.sprawlPublished by sprawl.toOfficial publisherv1.2.0Updated Oct 24, 2026
Stand up ops from Cursor/Claude/Codex; fleets keep running after your session ends.
Overview
A remote MCP endpoint that lets an assistant stand up operations from Cursor, Claude or Codex, with fleets that keep running after the session ends.
- What you can do
- Sprawl is a remote MCP server reached over streamable HTTP at its own endpoint. According to the description, it lets an assistant stand up ops from clients such as Cursor, Claude or Codex, and the fleets it starts keep running after your session ends. The manifest lists no tools, so the specific operations available are not documented here.
- When to use it
- Consider it when you want an assistant to launch operational workloads from a coding or chat client and have them persist beyond the conversation. It is less suitable if you need a documented tool list before adopting a server.
- Requirements
- A remote MCP client that supports streamable HTTP. Authentication is required via OAuth 2.1 with PKCE, discovered automatically at the server's well-known OAuth protected resource endpoint; browser-based clients such as Claude Code, Cursor and Claude.ai connectors are mentioned. The Authorization header carries the credential. No packages or environment variables are declared.
Installation
In SourceWeft
- Open Sprawl in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/to.sprawl%2Fsprawl/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"sprawl": {
"type": "http",
"url": "https://sprawl.to/api/mcp"
}
}
}Tools
0Version history
2- v1.2.0LatestOct 14, 2026
- v1.1.0Sep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.