Payment Gateway
Stripe MCP connector
The Stripe connector brings charges, refunds, disputes, customers and balance transactions into Claude, ChatGPT, Cursor and any MCP client, so your team can look up a payment, issue a refund or close a dispute by asking, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Stripe to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Stripe once
-
Open Connections, choose Add connection, and pick Stripe.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Stripe API key. One person generates a token in Stripe and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Stripe to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Stripe to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Stripe to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Stripe to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Stripe through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
Find the charge behind a customer complaint
A customer writes in about an amount they do not recognize. Ask for their charges by email or customer name, see what was billed and when, and answer them without opening a second tab.
-
Support
Issue a refund while the customer waits
Once you have confirmed the charge, ask for a full or partial refund on it and add a note explaining why. The refund lands in Stripe and the audit log records who issued it.
-
Finance
Reconcile the day's balance transactions
Pull the list of balance transactions for a date range, group them by type, and check the totals against what landed in the bank.
-
Finance
Review and respond to open disputes
Ask which disputes are open, read the reason on each one, add evidence notes, and close the ones the business has decided not to contest.
-
Sales
Catch the customer record up after a call
After a call, update the customer's name, email, billing details or description in Stripe so the next person who looks it up sees the current picture.
-
Operations
Capture held charges once the order ships
For payments that were authorized but not yet captured, ask for the ones waiting and capture each one as the order goes out the door.
Try asking
- “Show yesterday's failed charges and their refund status.”
- “Which open disputes need evidence this week?”
- “Summarize this month's balance transactions by payout.”
AI tools
Stripe tools for your AI agents
532 tools are ready to call through Elaichi's MCP endpoint the moment you connect Stripe, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Stripe gets you
6 screens from the product, each doing one job for your Stripe account.
The agent
Ask about charges, get answers from Stripe.
Plain language questions run against live Stripe charges, refunds and balance transactions.
- charges
- refunds
- disputes
- balance transactions
Ask Elaichi to work across your apps.
Show yesterday's failed charges and their refund status.
Which open disputes need evidence this week?
Summarize this month's balance transactions by payout.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Stripe here.
One org-wide MCP endpoint over OAuth, no SDK and no shared Stripe key.
Copy the endpoint
Tool catalog
532 Stripe tools are cataloged and ready.
Charges, disputes, refunds and balance transactions are covered with no custom code.
- Get single Stripe balance by ID
- Get single Stripe balance setting by ID
- Update a Stripe balance setting by ID
- List all Stripe balance transactions
Toolboxes
Every team gets its own Stripe toolbox.
Finance, support and growth each see a curated set of Stripe tools.
- Finance
- Support
- Revenue Operations
- Sales
Shared connections
Teammates use Stripe without seeing a key.
Each Stripe connection shows who connected it and which teams and members share it.
- Finance
- Support EMEA
- Revenue Operations
- Marketplace payouts
Audit log
Every Stripe call is written down.
When, who, what happened, type and resource for each charge, refund or dispute.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires and Stripe work finishes.
Fetch charges, group them, draft a digest, approve it, post back to Stripe.
Stripe digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch charges
Stripe
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Stripe
Queued
Collections and dashboards
Stripe numbers land before anyone asks.
Four metrics, fourteen days of charges and a team breakdown, refreshed on schedule.
Stripe health
Refreshed 4 minutes ago · every 15 minutes · from the charges collection
Charges
1,284 ↓ 12%
Refunds
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Charges created
Last 14 days
By team
Share of activity
Finance 34%
Support EMEA 27%
Revenue Operations 21%
Marketplace payouts 18%
FAQ
Frequently asked questions
How do I connect Stripe to Claude?
Connecting Stripe to Claude takes two steps. First, in Elaichi, choose Stripe and paste in a Stripe API key from your Stripe dashboard, which is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when prompted and Stripe is ready to use.
Does Stripe work with ChatGPT and Cursor as well as Claude?
Yes. Once Stripe is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Stripe once and every client your team uses picks it up.
What can an AI agent actually do with my Stripe data?
With Stripe connected, an agent can look up a customer and the charges against them, create or update customer records, issue and adjust refunds, capture charges that were authorized earlier, read and respond to disputes, and list balance transactions for reconciliation. Because Stripe exposes hundreds of actions, the agent searches for the right one as you ask, so short concrete requests such as "refund the last charge for [email protected]" work better than long paragraphs.
Does connecting Stripe give the AI access to my whole Stripe account?
Access to Stripe follows the API key that was connected and the person who signed in to Elaichi. If the Stripe key is restricted, the agent is restricted the same way. Elaichi can narrow that access further, for example to reading charges but never creating refunds, and it can never widen it beyond what Stripe itself allows.
Can I stop an agent from deleting or changing things in Stripe?
Yes. Restrictions in Elaichi apply to Stripe action by action, so you can allow looking up charges and customers while blocking deleting a customer, creating a refund or closing a dispute. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a Stripe connection when someone leaves?
When you offboard someone in Elaichi, their access to Stripe through every client ends at once, and the audit log keeps the record of what they did. A shared Stripe connection keeps working for everyone else on the team. If you ever want to remove Stripe entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Stripe in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.