Stripe MCP setup: start with a sandbox

An existing test environment is a useful starting point for your first connection. Choose one familiar test record and write down its identifier. This guide covers technical setup and a read request you can verify. It does not describe an executed payment or an authenticated test with your Stripe account. Keep the expected result separate from the response you later receive.

Choose the account and environment deliberately

Stripe documents remote MCP access at https://mcp.stripe.com. OAuth is available for interactive clients. Review which accounts and environments are selected during authorisation. Stripe describes sandboxes as separate test environments. Successful sign-in alone does not establish that the next request will use the environment you intended.

A complete VS Code connection

{
  "servers": {
    "stripe": {
      "type": "http",
      "url": "https://mcp.stripe.com"
    }
  }
}

Add this example to the MCP configuration for your chosen workspace. If the file already contains connections, add only stripe inside servers. Start the connection and follow the OAuth sign-in flow. This example does not require a copied API key. The VS Code guide explains the file structure; the converter helps with other configuration formats.

Read a test record and compare it

1. Open your sandbox in the Dashboard. Choose an existing test record and record its identifier plus one non-sensitive property.

2. After signing in, inspect the offered tools and their descriptions. Explicitly choose a read operation and identify the account and test record.

3. Compare the response with the Dashboard. Do the identifier, environment and expected property match? An empty response does not prove that the intended account has no data.

4. Record the procedure and observed result without credentials. Repeat the read test after changing account selection, permissions or client configuration.

Separate permission checks from error diagnosis

The tool list can include both read and write operations. Wording a task as a read request does not itself limit account permissions. Before proceeding, inspect the access actually granted. Use the permission planner to record the target, allowed operation and approval. Changes to real payment data do not belong in a basic connection test.

For access errors, first check sign-in, the selected environment and whether your organisation permits the connection. If a result is empty, compare the exact identifier with the Dashboard before creating new records. The troubleshooting navigator helps narrow down the cause. The registry search shows other implementations; the app directory organises related setup guides.

Common Stripe MCP questions

Does this example require an API key?

It uses the documented OAuth route. Choose the matching sign-in flow in your client and review the granted permissions.

Is a sandbox the same as live mode?

No. Check the selected environment and use only familiar test data for the first request.

Should I create a payment or refund to test the connection?

No. A known record and a read operation are enough for an initial access check. Write workflows need a separate test plan.

Why does the returned data differ from the Dashboard?

Compare the account, environment and record identifier first. Record any discrepancy before changing configuration or data.

Provider sources checked on 2 October 2026. The checks are proposals for your own environment.

1. Stripe MCP
   Show retrieval command

   curl -s https://docs.stripe.com/mcp
2. Stripe Sandboxes
   Show retrieval command

   curl -s https://docs.stripe.com/sandboxes

All posts