Skip to main content

Connect Stripe to VS Code

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

Set up

Add Stripe to VS Code in four steps

Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Stripe’s 10 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

10 Stripe tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination