Peach MCP connector

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.

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.

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.

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.

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.

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.

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.

Yes. Peach is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Yes. Both let Claude, ChatGPT or Cursor use Peach. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Peach call.

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Peach: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.