FetchSandbox

Connect it to your AI

Claude Code

claude mcp add --transport http fetchsandbox https://fetchsandbox.com/mcp/v1

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://fetchsandbox.com/mcp/v1

claude mcp add fetchsandbox -- npx -y fetchsandbox-mcp@0.7.30

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "fetchsandbox": {
      "url": "https://fetchsandbox.com/mcp/v1"
    }
  }
}

Tools it offers

8 tools, as the server itself reported during our check on Oct 31, 2026.

• coachConversational integration coach for FetchSandbox. Server-side orchestrator that walks the user through adding an API integration (payments / email / auth / etc.) — intake the goal, elicit domain-aware discovery question
• get_jobRetrieve the SAME running find_bugs, fix_bug, prove_fix, verify_behavior or validate_integration job (including requirements planning). Follow next_tool_call until status is done or error. Never restart the original tool
• guideROUTE a symptom to the provider behaviour that explains it. Use this when the user names a provider or a domain (payments, email, auth, SMS, subscriptions) and you need to know what that provider ACTUALLY does — not what
• quickrunRun a curated reference workflow against a KNOWN, bundled spec (stripe, clerk, descope, resend, twilio, and 50+ others) in ONE call — it spins up the sandbox by slug, so you do NOT need import_spec or a sandbox_id first.
• validate_integrationCompletion rule: a request to verify an app includes its applicable failure checks without another user prompt. When verification_continuation.required is true, continue in this agent: inspect pending_checks, preserve ev
• list_workflowsList the named, runnable workflows for a known provider slug or imported spec. Workflows are realistic multi-step API journeys (e.g. 'create customer → attach payment method → create subscription'). Known provider slugs
• run_workflowExecute ONE specific workflow by name and return its step-by-step trace PLUS a `share_url` — a public, replayable proof URL that renders the full timeline (every request, response, webhook event) for this run. The share_
• verify_behaviorProve a known fix survives a bug — the 'prove' half of reproduce→prove. The backend spawns a buggy AND a fixed reference handler and fires the bug_pattern's probes at both, returning the side-by-side diff (e.g. the buggy

Questions