# 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. Source: https://elaichi.ai/connectors/peach/ ## Facts | | | | --- | --- | | Application | Peach | | Category | Payment Gateway | | AI tools | 10 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Peach is connected - 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. ## Connect Peach in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Peach. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Peach tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Peach to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Peach to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Peach tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Peach through Elaichi ### Record a payment the moment it arrives Finance. 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. ### Find the transaction behind a query Finance. Search Peach transactions by the details a customer gives you and get the matching payment back in seconds when reconciling or answering a dispute. ### Catch the contact up after a call Support. 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. ### Add a new payer without leaving the conversation Sales. 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. ### Check how a campaign is performing Marketing. 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. ### Clean out stale contacts in one pass Operations. 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. ## 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 my team share one Peach connection? Yes. One person connects Peach in Elaichi with the API key and shares the connection with a team, and nobody else on the team ever handles the key or a credential. Each teammate still signs in to Elaichi as themselves, so every payment recorded or contact updated in Peach is logged under the name of the person who did it, not the person who connected it. ### 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. ## All 10 Peach tools Every tool below is callable through https://api.elaichi.ai/mcp once Peach is connected, subject to the toolbox it is in and the restrictions on the caller. - **Get single Peach campaign by ID** (Get). Get a specific peach campaign by id. Returns: updatedAt, type, limit, startDate, endDate. Required: id. - **Peach campaigns get stats** (Get). Get detailed public statistics for a specific peach campaign including total amount raised, donation count, and per-group breakdowns. Returns: limit, startDate, endDate. Required: account_id, campaign_id. - **Create a Peach payment** (Create). Create a payment in Peach. Returns the created payment object including paymentId, status, donationSum, donationCurrency, donorDisplayName, email, campaignId, and createdAt. Required: sum. Currency defaults to ILS; billingCycles is required when isSubscription is true. - **Update a Peach payment by ID** (Update). Update a payment in Peach by performing an action such as canceling a subscription, changing the charge day, freezing, or updating a payment field. Returns: message. Required: id, action. - **Create a Peach contact** (Create). Create a new contact in Peach. Returns: contactBody, contactResponse, contactId, failedCustomProperties. Required: firstName, lastName, email. - **Get single Peach contact by ID** (Get). Get a single Peach contact by contactId, email, phoneNumber, or tz. Returns: email, contactId. At least one of contactId, email, phoneNumber, or tz must be provided. - **Update a Peach contact by ID** (Update). Update an existing Peach contact by id. Returns: success, message, contact. Required: id. - **Peach contacts bulk delete** (Delete). Delete a Peach contact by contactId. Returns: success, message. Required: contactId. - **Peach interactions create note** (Create). Create a note for a contact in Peach. Returns the created note object (noteBody) with category, contactId, noteTitle, noteBody, and source, plus an interactionResponse identifier. Required: contactId, noteBody. - **List all Peach search transactions** (List). Search Peach transactions within a date range, optionally filtered by campaign. Returns: createdAt, updatedAt. Date range defaults to the last 30 days; max 1000 results per page.