Skip to main content
Book a demo

Connect Stripe to Windsurf

Give Windsurf governed access to Stripe’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Windsurf setup guide

Set up

Add Stripe to Windsurf in four steps

Admins approve the server once. Everyone in Windsurf then gets it through the same governed connection.

  1. 1

    Approve Stripe in Runlayer

    Add Stripe from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Windsurf to Runlayer

    Users add the Runlayer Plugin to Windsurf by following Runlayer’s setup guide. Windsurf reaches Stripe’s 10 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Windsurf setup guide
  3. 3

    Sign in to Stripe

    Sign in the way Stripe requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Stripe from Windsurf

    Stripe’s approved tools appear in Windsurf. Every call is checked against policy and recorded.

Tools

10 Stripe tools in Windsurf

Runlayer policy decides which of these Windsurf users can call.

  • List available accounts or orgs

    Lists all Stripe accounts in this session with their stripe_context and livemode values.

  • Manage Stripe accounts

    Returns a URL to the Stripe Dashboard where users can add accounts, remove accounts, or change permissions for this session.

  • Search Stripe documentation

    Search the Stripe documentation for the given question and language.

  • Send Stripe feedback

    Share feedback about Stripe's products.

  • Analytics

    Is for analyzing Stripe Sigma and Metrics data (e.g. about revenue, charges, products, invoices, subscriptions, disputes, transactions, tax tables, payments etc) and running SQL-based reporting…

  • API details

    Get detailed parameter information for a specific Stripe API operation.

  • Read API

    Use stripe_api_search to find the operation ID.

  • API search

    Search for Stripe API operations by providing an intent and a resource to operate on.

See all 10 Stripe tools

Control

What Runlayer can see and stop in Windsurf

Some controls apply to every client at the gateway. Others depend on what Windsurf exposes to Runlayer.

  • Gateway policy (available)

    Every Stripe call from Windsurf passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Windsurf as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Windsurf runs it.

  • Block output after it runs (not available)

    Windsurf ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Windsurf has no way to receive replacement output, so Runlayer cannot mask it. The gateway still applies policy to the call.

In Windsurf

  • Enforcement needs Windsurf 1.12.31 or newer.
  • When Runlayer denies a call, Windsurf shows the reason to the user; Runlayer cannot adjust the call’s inputs.

Frequently asked questions

Connect more

Find another combination