Connect Stripe to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Stripe’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Stripe to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Stripe in Runlayer
Add Stripe from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Stripe’s 10 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 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
Use Stripe from GitHub Copilot CLI
Stripe’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
10 Stripe tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot 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.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Stripe call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more