Skip to main content
Book a demo

Connect Stripe to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Stripe to Cline CLI in four steps

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

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

    Cline CLI 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 Cline CLI

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

Tools

10 Stripe tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Block output after it runs (not available)

    Cline CLI 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)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination