Payment Gateway
Peach MCP connector
The Peach connector brings your Peach payments, contacts, campaigns and transactions to Claude, ChatGPT, Cursor and any MCP client, so your team can look up, record and update payment activity in plain language while every action stays within each person's own Peach access.
-
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.
10 tools
How to connect
How to connect Peach to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Peach once
-
Open Connections, choose Add connection, and pick Peach.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Peach API key. One person generates a token in Peach 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 Peach 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 Peach 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 Peach 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 Peach 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 Peach through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Record a payment the moment it arrives
Create a new Peach payment against the right contact, or correct an amount or reference on an existing payment, without opening Peach and hunting for the record.
-
Finance
Find the transaction behind a query
Search Peach transactions by the details a customer gives you and get the matching payment back in seconds when reconciling or answering a dispute.
-
Support
Catch the contact up after a call
Pull up a Peach contact, update their details, and add a note about what was agreed so the next person to open the record already knows the story.
-
Sales
Add a new payer without leaving the conversation
Create a Peach contact from the details in an email or call, then set up their first payment, all from the chat window you are already working in.
-
Marketing
Check how a campaign is performing
Ask for the stats on a Peach campaign by name or ID and get the current numbers back for a weekly update, without waiting on someone to export them.
-
Operations
Clean out stale contacts in one pass
Identify the Peach contacts that are duplicates or no longer needed and remove them in bulk, with the deletion logged against the person who asked for it.
Try asking
- “Show failed Peach payments from the last seven days.”
- “Which Peach campaign drove the most transactions this month?”
- “Add a note to this Peach contact after refund.”
AI tools
Peach tools for your AI agents
10 tools are ready to call through Elaichi's MCP endpoint the moment you connect Peach, 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 Peach gets you
6 screens from the product, each doing one job for your Peach account.
The agent
Ask about Peach payments in plain language.
Questions about payments, contacts and campaigns answered from live Peach records.
- payments
- contacts
- campaigns
- transactions
Ask Elaichi to work across your apps.
Show failed Peach payments from the last seven days.
Which Peach campaign drove the most transactions this month?
Add a note to this Peach contact after refund.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Reach Peach from any MCP client.
Claude, ChatGPT and Cursor connect over one org endpoint, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
10 Peach tools ready without custom code.
Payments, contacts, campaigns and transaction search exposed as callable methods.
- Get single Peach campaign by ID
- Peach campaigns get stats
- Create a Peach payment
- Update a Peach payment by ID
ElaichiToolsToolboxes
Every team gets its own Peach toolbox.
Finance, support and growth each see the Peach tools their work needs.
- Finance
- Support
- Growth
- Revenue operations
ElaichiToolboxesShared connections
Teammates use Peach without seeing credentials.
One connected Peach account, shared to named teams and members, credentials stay hidden.
- Finance core
- Support EMEA
- Growth
- Revenue ops
ElaichiConnectionsAudit log
Answer who changed which Peach payment.
Every call logged with time, person, action, type and Peach resource touched.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 runs your Peach reconciliation end to end.
Fetch payments, group them, draft a digest, get approval, post back to Peach.
Peach digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch payments
Peach
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
Peach
Queued
Collections and dashboards
Peach payment health, counted not guessed.
Four metrics, 14 days of payments created and a team breakdown, refreshed on schedule.
Peach health
Refreshed 4 minutes ago · every 15 minutes · from the payments collection
Payments
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Payments created
Last 14 days
By team
Share of activity
Finance core 34%
Support EMEA 27%
Growth 21%
Revenue ops 18%
FAQ
Frequently asked questions
How do I connect Peach to Claude?
Connecting Peach to Claude takes two steps. First, connect Peach in Elaichi: Peach uses an API key, so you paste the key from your Peach account into Elaichi and the connection is ready, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste in https://api.elaichi.ai/mcp. Sign in as yourself and Peach is available in your Claude conversations.
Does Peach work with ChatGPT and Cursor as well as Claude?
Yes. Once Peach 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 Peach once and every client your team uses can reach it.
What can an AI agent actually do with my Peach data?
With Peach connected through Elaichi, an AI agent can create and update payments, create and update contacts, look up a single contact or campaign, pull stats for a campaign, add a note to a contact's interaction history, search your transactions and remove contacts in bulk. In practice that means asking things like "find the payment from Jane Ortiz last Tuesday", "add a note that she asked for a receipt" or "how is the spring campaign doing" and getting the answer or the change made in Peach directly.
Does connecting Peach give the AI access to all our payments and contacts?
No. When Peach is connected through Elaichi, every request runs as the person who signed in, so an agent can only see and change the Peach payments, contacts and campaigns that person could already reach in Peach. Elaichi can narrow that further by restricting which actions are available to a team or role, but it can never widen access beyond what Peach itself grants that person.
Can I stop an agent from deleting or changing things in Peach?
Yes. Restrictions in Elaichi work per action, so you can allow reading Peach contacts and transactions while blocking the ability to create or update payments, edit contacts or delete contacts in bulk. A blocked action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.
What happens to a Peach connection when someone leaves?
When you offboard someone in Elaichi, their access to Peach through every client ends at once, and the audit log keeps the record of what they did while they were here. If they connected a shared Peach connection, it keeps working for everyone else on the team. If you ever want to remove Peach entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Peach in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.