# Givebutter MCP connector

The Givebutter connector brings campaigns, tickets, discount codes, campaign teams and contact activities to Claude, ChatGPT and Cursor, so each person can ask about and update their fundraising inside their own Givebutter access, with every call logged.

Source: https://elaichi.ai/connectors/givebutter/

## Facts

| | |
| --- | --- |
| Application | Givebutter |
| Category | CRM |
| AI tools | 70 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Givebutter is connected

- List every live discount code on the spring gala campaign
- Log a thank-you call activity on this donor's contact
- Which campaign teams have joined the walkathon so far?

## Connect Givebutter in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Givebutter.
2. Optionally set Share with, then press Connect.
3. Paste a Givebutter API key. One person generates a token in Givebutter 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 Givebutter tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Givebutter MCP connector for 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.

## Givebutter MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Givebutter MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

## Givebutter MCP connector for 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.

## Givebutter MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Givebutter 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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Givebutter tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Givebutter through Elaichi

### Log the call before you forget it

Development. After a donor call, add the conversation to the contact's activity history in Givebutter so the next person sees what was discussed and what was promised.

### Issue tickets for the gala without the dashboard

Events. Create tickets for a campaign and check who already holds one, straight from a chat, while you are still on the phone with the guest.

### Set up a sponsor discount code in minutes

Marketing. Create, update or retire a campaign discount code for a sponsor push, then list what codes are live before the email goes out.

### Check how a peer-to-peer campaign is doing

Development. List the campaign teams and members on a walkathon or giving day to see which teams have joined and who is actually fundraising.

### Tidy up campaign records after an event

Operations. Remove a duplicate campaign member or a team that never launched, and update the campaign details once the dust settles.

### Prepare for a meeting with one donor

Donor relations. Pull a contact's recent activities and the campaigns they are tied to before you walk in, so the conversation starts where the last one ended.

## Elaichi vs Zapier MCP vs Composio for Givebutter

All three can connect Givebutter to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Givebutter tools | Allow or restrict single Givebutter tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Givebutter call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Givebutter to Claude?

Connect Givebutter in Elaichi by pasting your Givebutter API key, which you copy from your Givebutter account settings. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, so the whole thing takes a few minutes.

### Does Givebutter work with ChatGPT and Cursor as well as Claude?

Yes. Once Givebutter is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Givebutter once and every client picks it up.

### What can an AI agent actually do with my Givebutter data?

An agent can create and update Givebutter campaigns, issue campaign tickets, create and retire discount codes, list campaign teams and members, and add or update activities on a contact. In practice that means asking for the state of a campaign, logging a donor conversation, or setting up a sponsor discount code in plain language. Short, concrete asks such as "list live discount codes for the spring gala" work better than long paragraphs.

### Does connecting Givebutter give the AI everything in my account?

No. Every call to Givebutter runs under the access of the person who connected it, so the agent sees exactly what that Givebutter account can see and nothing more. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Givebutter itself allows.

### Can my team share one Givebutter connection?

Yes. One person connects Givebutter in Elaichi and shares the connection with a team, and nobody else ever handles the Givebutter API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who created a ticket or deleted a campaign, not a shared account.

### Can I stop an agent from deleting or changing things in Givebutter?

Yes. In Elaichi you can restrict any single Givebutter action, such as deleting a campaign or removing a campaign member, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Givebutter connection when someone leaves?

When someone is offboarded in Elaichi, their access to Givebutter through every client ends at once. A Givebutter connection they were sharing keeps working for everyone else on the team. If you disconnect Givebutter in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Givebutter MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Givebutter 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, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Givebutter?

Yes. Both let Claude, ChatGPT or Cursor use Givebutter. 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 Givebutter call.

### How is Elaichi different from Composio for Givebutter?

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 Givebutter: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 70 Givebutter tools

Every tool below is callable through https://api.elaichi.ai/mcp once Givebutter is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Givebutter campaign discount code** (Create). Create a discount code. Required: campaign_id, type, active, amount, code.
- **Delete a Givebutter campaign discount code by ID** (Delete). Delete a discount code. Required: id, campaign_id.
- **Get single Givebutter campaign discount code by ID** (Get). Get a discount code. Required: id, campaign_id.
- **List all Givebutter campaign discount codes** (List). List all discount codes. Required: campaign_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Update a Givebutter campaign discount code by ID** (Update). Update a discount code. Required: id, campaign_id, amount.
- **Delete a Givebutter campaign member by ID** (Delete). Delete a campaign member. Required: id, campaign_id.
- **Get single Givebutter campaign member by ID** (Get). Get a campaign member. Required: id, campaign_id.
- **List all Givebutter campaign members** (List). List all campaign members. Required: campaign_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Delete a Givebutter campaign team by ID** (Delete). Delete a campaign team. Required: id, campaign_id.
- **Get single Givebutter campaign team by ID** (Get). Get a campaign team. Required: id, campaign_id.
- **List all Givebutter campaign teams** (List). List all campaign teams. Required: campaign_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Create a Givebutter campaign ticket** (Create). Create a campaign ticket. Required: campaign_id, name, price.
- **Get single Givebutter campaign ticket by ID** (Get). Get a campaign ticket. Required: id, campaign_id.
- **List all Givebutter campaign tickets** (List). List all campaign tickets. Required: campaign_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Create a Givebutter campaign** (Create). Create a campaign. Required: type, title.
- **Delete a Givebutter campaign by ID** (Delete). Delete a campaign. Required: id.
- **Get single Givebutter campaign by ID** (Get). Get a campaign. Required: id.
- **List all Givebutter campaigns** (List). List all campaigns. The connector pages through all results (100 per page, or your limit up to 100).
- **Update a Givebutter campaign by ID** (Update). Update a campaign. Required: id.
- **Create a Givebutter contact activity** (Create). Create a contact activity. Required: contact_id, type.
- **Delete a Givebutter contact activity by ID** (Delete). Delete a contact activity. Required: id, contact_id.
- **Get single Givebutter contact activity by ID** (Get). Get a contact activity. Required: id, contact_id.
- **List all Givebutter contact activities** (List). List all contact activities. Required: contact_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Update a Givebutter contact activity by ID** (Update). Update a contact activity. Required: id, contact_id.
- **Givebutter contact tags bulk delete** (Delete). Remove tags from a contact. Required: contact_id, tags. Removes the listed tags (POST .../tags/remove); the others stay.
- **Givebutter contact tags bulk update** (Update). Sync tags for a contact. Required: contact_id, tags. Replaces the contact's whole tag set with exactly these tags (POST .../tags/sync); others are removed.
- **Create a Givebutter contact tag** (Create). Add tags to a contact. Required: contact_id, tags. Adds the listed tags (POST .../tags/add); the contact's other tags stay.
- **Create a Givebutter contact** (Create). Create a contact.
- **Delete a Givebutter contact by ID** (Delete). Delete a contact. Required: id.
- **Get single Givebutter contact by ID** (Get). Get a contact. Required: id.
- **List all Givebutter contacts** (List). List all contacts. The connector pages through all results (100 per page, or your limit up to 100).
- **Givebutter contacts restore** (Restore). Restore a contact. Required: contact_id.
- **Update a Givebutter contact by ID** (Update). Update a contact. Required: id. Sending tags replaces the contact's whole tag set; leave tags out to keep them.
- **Create a Givebutter fund** (Create). Create a fund. Required: name.
- **Delete a Givebutter fund by ID** (Delete). Delete a fund. Required: id.
- **Get single Givebutter fund by ID** (Get). Get a fund. Required: id.
- **List all Givebutter funds** (List). List all funds. The connector pages through all results (100 per page, or your limit up to 100).
- **Update a Givebutter fund by ID** (Update). Update a fund. Required: id, name.
- **Create a Givebutter household contact** (Create). Add a contact to a household. Required: household_id, contact_id.
- **Delete a Givebutter household contact by ID** (Delete). Remove a contact from a household. Required: id, household_id.
- **Get single Givebutter household contact by ID** (Get). Get a contact associated with a household. Required: id, household_id.
- **List all Givebutter household contacts** (List). List all contacts associated with a household. Required: household_id. The connector pages through all results (100 per page, or your limit up to 100).
- **Create a Givebutter household** (Create). Create a household. Required: name.
- **Delete a Givebutter household by ID** (Delete). Delete a household. Required: id.
- **Get single Givebutter household by ID** (Get). Get a household. Required: id.
- **List all Givebutter households** (List). List all households. The connector pages through the results (page by page; your limit sets per_page, up to 100).
- **Update a Givebutter household by ID** (Update). Update a household. Required: id.
- **Get single Givebutter message by ID** (Get). Get a message. Required: id.
- **List all Givebutter messages** (List). List all messages. The connector pages through all results (100 per page, or your limit up to 100).
- **Get single Givebutter payout by ID** (Get). Get a payout. Required: id.
- ...and 20 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
