Skip to main content
FetchSandbox Docs

Quickstart

Make a discovery call, then test your actual app.

1. Make the first call

Connect to the remote MCP server using MCP setup. Then run list_workflows(spec_slug=stripe). It's a read-only discovery call. See first tool call.

2. Add your account key

Get a key from /keys. Keep it in your private client config and never paste it into chat.

3. Test your actual app

Start by agreeing on the expected behavior. Configure the twin URLs and temporary credentials, and expose a protected, reachable trigger and observable state. Then call validate_integration. While the job runs, keep polling the same get_job.

4. Local or hosted

A local app needs an active tunnel. A protected n8n Cloud webhook doesn't need a tunnel on your laptop.

To see what's ready now, check Availability.

Confirm an actual tool call
Call FetchSandbox list_workflows with spec_slug stripe and tell me the actual result.
Verify your running app and inspect a receipt
Use FetchSandbox validate_integration for this running app. Agree the observable expected behavior with me, configure the isolated twins, invoke the actual app and report the receipt, including anything failed or unmeasured. Keep polling the same get_job until it reaches a terminal state.