← fetchsandbox.com
INDIVIDUAL MCP TOOL
list_workflows
List the named, runnable workflows for a previously-imported spec.
LIVE ENDPOINT
https://fetchsandbox.com/mcp/v1
Connect to this endpoint to inspect the live schema for list_workflows and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.fetchsandbox]
url = "https://fetchsandbox.com/mcp/v1"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"fetchsandbox": {
"type": "http",
"url": "https://fetchsandbox.com/mcp/v1"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: fetchsandbox
Remote MCP URL: https://fetchsandbox.com/mcp/v1
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"fetchsandbox": {
"url": "https://fetchsandbox.com/mcp/v1"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"fetchsandbox": {
"type": "http",
"url": "https://fetchsandbox.com/mcp/v1"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "fetchsandbox",
"transport": "streamable-http",
"url": "https://fetchsandbox.com/mcp/v1"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
coach— Conversational integration coach for FetchSandbox.find_bugs— FIRST STEP for any API-integration bug — webhooks, payments, auth, email, SMS, subscriptions.fix_bug— FetchSandbox remediation: get a proposed fix for a specific bug in YOUR code.prove_fix— THE PROOF STEP.guide— ROUTE a symptom to the provider behaviour that explains it.quickrun— Run a curated proof 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.list_specs— Browse the FetchSandbox spec catalog — every API (Stripe, GitHub, Twilio, Notion, OpenAI, Polar, GitLab, and 40+ more) that has a ready-to-use sandbox with curated workflows.import_spec— Ingest an OpenAPI spec and get a working sandbox you can call immediately.