Stripe Legacy MCP for AI. See real-time payments, customer data, and balances in chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
Stripe Legacy connects your AI agent directly to core Stripe payment APIs. It lets you manage payments, check account balances, create refunds, and handle customer data without logging into a separate dashboard.
You run full financial operations—from listing charges to creating tokens—using simple chat commands.
What AI agents can do with Stripe Legacy Automation
Create charge
Processes and records a new monetary charge against a customer or token.
Create customer
Creates a new record for a client within your Stripe account.
Create refund
Issues money back to the original source of a completed charge.
The tool retrieves your current Stripe balance and pending funds.
It fetches lists of charges, invoices, or subscriptions based on filters you provide.
You can create new charges, issue refunds, or generate single-use payment tokens.
The tool lets you view and retrieve specific customer profiles by ID.
Ask an AI about this
Waiting for input…
What AI agents can do with Stripe Legacy: 11 Tools for Financial Operations
These tools let you run every core payment function—from creating charges to listing subscriptions—within a single AI agent session.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Stripe Legacy on VinkiusCreate Charge
Processes and records a new monetary charge against a customer or token.
Create Customer
Creates a new record for a client within your Stripe account.
Create Refund
Issues money back to the original source of a completed charge.
Create Token
Generates a temporary, single-use payment token from sensitive card data.
Get Balance
Retrieves the current available and pending balance for your Stripe account.
Get Charge
Pulls all details for one specific transaction ID.
Get Customer
Retrieves the profile and billing information for a specified customer.
List Charges
Lists multiple past charges, allowing you to filter by date or status.
List Customers
Retrieves a list of all customer IDs and basic profile data.
List Invoices
Fetches records for billing invoices, useful for auditing payments owed.
List Subscriptions
Lists all currently active recurring payment plans and their status.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Stripe Legacy integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Stripe Legacy, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Stripe. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Checking Stripe balances shouldn't take 5 clicks and a login., Solved with Vinkius AI Gateway
Today, checking your account balance means opening the Stripe dashboard. You navigate to the 'Dashboard' tab, then find the 'Balances' section, and finally read the figure on the screen. It’s slow, it requires context switching, and sometimes the data you need is buried under a bunch of graphs.
With this MCP server, that process vanishes. You just ask your agent: 'What's my available Stripe balance?' The agent runs `get_balance` and spits out the number—available vs. pending—right in your chat window. No dashboard needed; you get the data instantly.
Stripe Legacy MCP Server: Control payments from your terminal.
Manual payment control used to mean writing multi-step scripts: first calling an API to list charges, then parsing that JSON to find the ID you wanted to refund, and finally executing a separate refund call using that extracted ID. It’s fragile, error-prone, and takes time.
Now, you just tell your agent, 'Refund the charge with ID ch_xyz.' The server handles the entire sequence—retrieving the necessary context and calling `create_refund`—in one smooth operation. You're done.
What your AI can actually do with this
Listen up. This Stripe Legacy connection lets your AI agent talk straight to your core Stripe APIs, managing everything from payments and refunds to client accounts without you having to log into a damn dashboard. You run full financial ops—from listing old charges to creating new customer tokens—using nothing but simple chat commands.
Managing Money Flow: Charging, Tokens, and Refunds
You can process money right out of the gate. Use create_charge to process and record any new monetary charge against a specific customer or payment token. When you need to capture sensitive card data temporarily before making a charge, run create_token, which generates that single-use payment token for you. If you're dealing with payouts, remember you can always issue money back using create_refund against the original source of any completed charge.
For quick cash flow checks, get_balance pulls up your current available and pending Stripe funds immediately. Need to know what went down on a specific day? You grab all details for one transaction ID using get_charge. If you need an overview of past activity, running list_charges lets you pull multiple charges while filtering by date or status.
Client Accounts: Creating and Viewing Customers
Handling customers is simple. First, you'll use create_customer to make a brand new record for any client in your Stripe account. To check out an existing client's profile and billing data, just call get_customer with their ID. If you need to see who you've done business with generally, list_customers retrieves a list of all customer IDs along with basic profile info.
Reporting and Auditing: Seeing What’s Happening
Want to audit your books? There are several ways to pull reports. You can use list_invoices to fetch records for billing invoices, which is killer when you're auditing payments that clients owe. If you deal with recurring services, list_subscriptions lists every active payment plan and what status they’re in. For a comprehensive view of historical transactions, running list_charges gives you multiple past charges, letting you filter them down by date or by their current status.
How It Works, Straight Talk
Your AI client takes your request—like 'refund the last charge for John Doe'—and translates it into a function call. This server executes that command directly against your live Stripe account credentials, giving you real-time data and completing the action without any manual steps on your end.
019dd169-d836-7152-8dad-65948bedb3fd 
Here's how it actually works
The bottom line is: you get real-time access to Stripe's financial API directly within your chat client.
Subscribe to the Stripe Legacy server on Vinkius.
Input your Stripe Secret Key (sk_...) into the configuration; this authenticates your connection.
Ask your AI agent to perform a payment action, like 'List charges from yesterday.' The agent executes the tool and returns the data.
Who is this actually for?
This server is for anyone dealing with billing complexity. It targets the support specialist tired of jumping between CRM, dashboard, and payment screens just to resolve one charge dispute. Or maybe the finance analyst who needs a quick audit without writing boilerplate API code.
They use this to instantly pull up detailed customer charges or list recent invoices when a client calls about billing issues.
They check the get_balance tool and run reports using list_charges to reconcile accounts quickly for month-end closing.
They test core payment flows—like running a charge followed by a refund—directly in the chat environment before committing code.
What Changes When You Connect
Instantly audit revenue flow. Instead of digging through a dashboard to check recent activity, just ask the agent to list_charges for the last 7 days. You get summaries immediately.
Stop manual balance checks. The get_balance tool gives you your available and pending funds in seconds—no need to open Stripe's financial overview page.
Handle billing disputes faster. If a customer needs proof of payment, ask for the charge details using get_charge. It pulls up every metadata point instantly.
Manage recurring revenue easily. Use list_subscriptions to see all active plans and their status, letting you quickly identify accounts that need attention.
Streamline payouts and refunds. When a refund is needed, create_refund handles the API call immediately, tracking it against the original charge for your records.
See it in action
Billing Inquiry Resolution
A client calls questioning a $50 charge from last week. Instead of asking the customer to email screenshots, you ask your agent to get_charge using the transaction ID provided. The agent instantly returns the full details—when it happened, who paid, and how much was processed. Problem solved in three seconds.
End-of-Month Reconciliation
The finance team needs to confirm total revenue for a specific product line. They ask the agent to list_charges and filter by keywords or date ranges. The system aggregates the data, showing successful charges vs. failed attempts, giving an immediate audit snapshot.
Onboarding New Users
You need to onboard a new client account in Stripe's database first. You run create_customer with their required details (name, email). Then, you immediately use the resulting customer ID to create_charge, ensuring the payment flows correctly from start to finish.
Debugging Failed Payments
A critical client reports a card failure. You first run get_customer to ensure their account is up-to-date, then use list_subscriptions to confirm if the payment was linked to an active plan. This rapid data gathering helps pinpoint whether it's a billing issue or a tokenization error.
The honest tradeoffs
Treating Stripe like a simple database.
A developer might try to list all charges and then manually loop through the result set in their code to find the customer's email, treating it like a basic SQL SELECT statement.
Don't iterate everything client-side. If you need specific customer details, run list_charges first for transaction context, then use the resulting ID list to call get_customer specifically. This limits unnecessary data retrieval.
Forgetting about idempotency.
Running a payment process twice because the user hit 'send' twice or the network hiccupped, leading to double billing charges.
Always use unique identifiers (like transaction IDs) when calling create_charge or create_refund. The API tools handle idempotency, but you must provide the correct keys.
Mixing up tokens and customers.
Trying to charge a card that was only used once (a token) without knowing which customer record it belongs to. This leaves your records incomplete or inaccurate.
Always establish the create_customer record first. Then, use the resulting Customer ID when calling create_charge. Tokens are temporary; customer IDs stick around.
When It Fits, When It Doesn't
Use this server if your primary need is to read or write core financial data: checking balances (get_balance), listing transactions (list_charges), managing subscribers (list_subscriptions), or processing payments/refunds. It's the go-to tool for any billing operation.
Don't use it if you just need general user profile management (use a dedicated CRM integration) or if your payment flow requires complex, non-financial logic, like calculating international sales tax or running an internal loyalty point system. For those tasks, you still need to write code that consumes the data after these tools provide it.
Questions you might have
How do I check my Stripe balance using get_balance? +
You simply ask your agent to 'Check my current account balance.' The get_balance tool executes and returns the available, pending, and total funds in a readable format.
Can I refund a charge with create_refund? What do I need? +
Yes. To use create_refund, you must provide the ID of the original charge that was paid. The tool handles the actual money movement and records it in Stripe.
How do I list all my active subscriptions using list_subscriptions? +
Ask your agent to 'List all active subscriptions.' The list_subscriptions tool pulls down a roster of current recurring payment plans, helping you audit your revenue streams.
What is the difference between get_charge and list_charges? +
get_charge fetches details for one specific charge ID. list_charges pulls a batch of charges (e.g., all from last month), allowing you to review many transactions at once.
If a new client signs up, what is the proper workflow for using `create_customer`? +
You must use create_customer first. This establishes a unique record in Stripe's system before any transactions occur. You pass basic identifying data—like email and name—to create that necessary customer account.
How does using `create_token` improve security when I make a payment? +
The token converts sensitive card details into a single-use placeholder. Instead of sending raw credit card numbers to the agent, you pass this safe token. This keeps your main API keys protected.
What is the difference between `list_charges` and using `list_invoices`? +
While both list transactions, invoices capture a complete billing cycle record. You use list_invoices to see everything billed—including payments and outstanding balances—whereas list_charges focuses only on raw transaction events.
When I run `list_customers`, how do I retrieve data for thousands of users? +
The system handles large datasets using pagination. You don't need to worry about hitting an artificial limit; the agent requests results in chunks until it confirms it has gathered every customer record available.
How do I find my Stripe Secret Key? +
Log in to your Stripe dashboard, navigate to Developers > API keys, and you will find your Secret Key (starting with sk_live_ or sk_test_) there.
We've already built the connector for Stripe Legacy. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.