Stand up ops from Cursor/Claude/Codex; fleets keep running after your session ends.
Connect Remote server
claude mcp add --transport http sprawl https://sprawl.to/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"sprawl": {
"url": "https://sprawl.to/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"sprawl": {
"type": "http",
"url": "https://sprawl.to/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://sprawl.to/api/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | OPTIONAL. This server supports OAuth 2.1 with PKCE, discovered automatically at /.well-known/oauth-protected-resource — browser-based clients (Claude Code, Cursor, Claude.ai connectors, and similar) should use that and need no header at all. Supply this header only for headless, CLI, or CI callers… |
Details
| Endpoint | https://sprawl.to/api/mcp (Streamable HTTP) |
| First published | 13 Oct 2026 |
| Last updated | 13 Oct 2026 |
| Registry name | to.sprawl/sprawl |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
