Skip to main content
FetchSandbox Docs

Example: first read-only MCP call

A read-only remote MCP call that lists Stripe workflows. It doesn't run anything against a Stripe twin or verify your app.

Before you start

This call only lists workflows and doesn't verify your app. On 14 Nov 2026 it ran without an account key, and authenticated actual-app verification is a separate step.

Request

A JSON-RPC tools/call request for list_workflows with spec_slug set to stripe. The exact recorded protocol request, curl command and connection prompt are each shown separately.

Connection prompt
Call FetchSandbox list_workflows with spec_slug stripe and tell me the actual result.
Request
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "list_workflows",
    "arguments": {
      "spec_slug": "stripe"
    }
  }
}
Protocol request
curl --request POST 'https://fetchsandbox.com/mcp/v1' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_workflows","arguments":{"spec_slug":"stripe"}}}'

Response excerpt

On 14 Nov 2026 it returned HTTP 200 and 29 workflows, including accept_payment. This is an excerpt of the response, which can arrive as text/event-stream.

HTTP 200 · 2026-11-14

Observed response
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\n  \"workflows\": [\n    {\n      \"id\": \"accept_payment\",\n      \"name\": \"Accept a one-time payment\",\n      \"description\": \"Create a PaymentIntent, confirm it, capture, and verify it succeeded\",\n      \"steps_count\": 5\n    }\n  ]\n}"
      }
    ]
  }
}

Next step

Set up your builder connection. Then agree on the actual-app contract before you test your app.

MCP setup · Behavioral contract