Givebutter
Givebutter is a fundraising platform that offers a free, open, and public API for developers to manage campaigns, track donations, and engage with supporters.
Verdict
Common use cases
- Pull donor transaction reports during board meetings
- Create new fundraising campaigns from Slack threads
- Archive outdated contacts in bulk cleanup sprints
- Set up webhooks for real-time donation Slack alerts
- Delete test campaigns after staging reviews
Integration
- Vendor
- Givebutter
- Category
- other
- Auth
- API_KEY
- Tools
- 18
- Composio slug
givebutter
Tools
- Archive Contact
Tool to archive a contact by their id. use after ensuring the contact has no associated data (e.g., no transactions or communications). example: "archive contact abc123".
- Create Campaign
Tool to create a new campaign. use when you have title, description, goal, and type ready, after confirming your givebutter account is authenticated.
- Create Webhook
Tool to create a new webhook subscription. use when you need to receive real-time notifications programmatically after confirming your endpoint can validate givebutter's signing secret.
- Delete Campaigndestructive
Tool to delete a campaign by its id. use after confirming the campaign has no funds raised. example: "delete campaign abc123".
- Delete Contactdestructive
Tool to delete a contact by their id. use after confirming the contact has no associated data (e.g., no transactions or communications). example: "delete contact abc123".
- Delete Funddestructive
Tool to delete a fund by its id. use when you need to remove a fund after confirming it exists. example: "delete fund fund abc123".
- Delete Webhookdestructive
Tool to delete a webhook by its id. use when you need to remove an obsolete webhook after confirming no further events are needed. example: "delete webhook abc123".
- Get Fund
Tool to retrieve details of a specific fund by its id. use after confirming the fund id is valid.
- Get Members
Tool to retrieve a paginated list of members for a given campaign. use when you need to list or process campaign members.
- Get Payouts
Tool to retrieve a list of payouts associated with your account. use when you need to list withdrawal transactions after authentication.
- Get Plans
Tool to retrieve a list of plans associated with your account. use after authentication to fetch recurring donation plans.
- Get Teams
Tool to retrieve a list of teams for a specific campaign. use after creating or updating a campaign when you need to list fundraising teams. example: "get teams for campaign camp123".
- Get Tickets
Tool to retrieve a list of tickets. use when you need to list all tickets for your account after authentication.
- Get Transactions
Tool to retrieve a list of transactions associated with your account. use when you need to list all donations and payments, optionally filtered by scope.
- Get Webhooks
Tool to retrieve all webhooks configured for your account. use after obtaining valid authentication.
- Update Campaign
Tool to update an existing campaign's details by its id. use when you need to modify campaign attributes after creation.
- Update Contact
Tool to update an existing contact's details by contact id. use when modifying contact information after confirming the contact id. only provided fields will be updated.
- Update Webhook
Tool to update an existing webhook subscription's details. use when you need to modify a webhook's name, url, trigger events, or enabled state after confirming its id. example: "update webhook wh 1234567890 to point to https://example.com/h
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Givebutter from the list. 3. Log into your Givebutter account, go to Settings > API, and generate a new API key with read and write permissions. 4. Paste the key into Switchy's connection form and click 'Connect'. 5. Return to any Space and type '@Givebutter list campaigns' to confirm the connection works — you should see your active campaigns. 6. To invoke a tool, @mention Givebutter in a message and describe what you need in plain language, like '@Givebutter create a campaign for our spring gala with a $50,000 goal'. The assistant will call the appropriate tool and return results inline.
What teammates see: by default, memories from Givebutter are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Campaigns
@Givebutter list all active campaigns and show me their titles, goals, and amounts raised so farOpen in a Space →
Create Spring Gala Campaign
@Givebutter create a campaign titled 'Spring Gala 2025' with a $75,000 goal and description 'Annual fundraiser supporting youth programs'Open in a Space →
Archive Inactive Contacts
@Givebutter find contacts with no transactions in the last 12 months and archive them after confirming they have no pending communicationsOpen in a Space →
Set Up Donation Webhook
@Givebutter create a webhook pointing to https://hooks.slack.com/services/T00/B00/XXX that fires on new transactionsOpen in a Space →
Pull Fund Details
@Givebutter get details for fund ID fund_abc123 including balance and recent transactionsOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Givebutter list all active campaigns with their current fundraising totals and goal amounts
Here are your active Givebutter campaigns: 'Annual Gala 2024' has raised $12,450 of its $25,000 goal (49.8%), 'Summer Camp Scholarships' has raised $3,200 of its $10,000 goal (32%), and 'Building Fund' has raised $48,900 of its $100,000 goal (48.9%). All three campaigns are currently live and accepting donations. This data reflects the state of your account at the time of the query.
This example shows the MCP's read capability for campaign data. Requires an API key with read access to campaigns. Fundraising totals update in real-time on Givebutter's side, so the figures shown here are illustrative snapshots, not live-synced values.
@Givebutter create a new campaign called 'Holiday Toy Drive' with a $5,000 goal for collecting donations through December
I've created the 'Holiday Toy Drive' campaign in your Givebutter account with a $5,000 fundraising goal. The campaign is now live and has been assigned ID camp_xyz789. You can customize the campaign page, add images, and configure donation tiers directly in your Givebutter dashboard. The campaign URL is givebutter.com/your-org/holiday-toy-drive.
This example demonstrates the MCP's write capability for campaign creation. Requires an API key with write permissions. The MCP creates the campaign structure, but visual customization (images, branding, custom fields) must be completed in Givebutter's web interface. Campaign IDs are generated by Givebutter upon creation.
@Givebutter pull all contacts who donated in the last 30 days and draft a thank-you email template acknowledging their recent support
I found 47 contacts who donated in the past 30 days. Here's a draft thank-you email: 'Dear [First Name], Thank you for your generous donation of [Amount] to [Campaign Name] on [Date]. Your support directly enables our mission to [mission statement]. We're grateful to have you in our community. With appreciation, [Your Organization].' This template uses merge fields compatible with most email platforms. You can personalize further or export the contact list for your CRM.
This example shows the MCP pairing contact data retrieval with AI-generated content. Requires read access to contacts and transactions. The contact list reflects Givebutter's data at query time; for large donor bases, consider filtering by campaign or donation amount to avoid rate limits on the contacts endpoint.
Use-case deep-dives
When Givebutter MCP makes sense for quarterly donor hygiene
A 3-person nonprofit runs quarterly donor list audits to archive duplicate contacts and remove test campaigns from their Givebutter dashboard. The MCP's 18 tools handle the repetitive delete/archive work without opening the web UI for each record. You'll need an API key from Givebutter's settings, then the MCP can batch-process contact archives or campaign deletions based on criteria you define in the prompt. The threshold: if you're only cleaning up 5-10 records per quarter, the web UI is faster than setting up the MCP. But if you're merging donor lists after an event or deduplicating 50+ contacts, the MCP pays off in the first session. Best for teams that run multiple campaigns per year and need programmatic cleanup between fundraising cycles.
Bulk campaign creation for multi-chapter organizations
A regional advocacy group with 8 local chapters launches identical fundraising campaigns for each chapter every quarter. The Create Campaign tool lets one person template the campaign structure (title, goal, description, type) and spin up all 8 variants in a single Switchy session instead of clicking through the Givebutter UI eight times. The MCP also exposes fund and webhook creation, so you can wire up Slack notifications or Zapier triggers as you build each campaign. The catch: Givebutter's API doesn't support cloning campaigns with all their media assets, so you'll still need to upload images and videos manually per campaign. Use this MCP when your campaign structure is text-heavy and your chapters need identical goals and descriptions, not when visual branding varies by location.
Webhook setup for auction night or telethon monitoring
A 5-person event team runs a live auction night and wants donation alerts piped into a Slack channel as bids come in. The Create Webhook tool registers a Givebutter webhook pointing to your Slack integration endpoint, and the MCP handles the signing secret validation setup. You define the event types (transaction.succeeded, campaign.goal_reached) in the tool call, and Givebutter starts pushing JSON payloads to your endpoint within seconds. The trade-off: you need a public HTTPS endpoint that can validate Givebutter's signature, which means either a Zapier webhook or a small serverless function. If your team doesn't have a developer and you're only running one event per year, Givebutter's built-in email notifications are simpler. But for recurring events or teams that already pipe data into Slack, the MCP's webhook tools are the fastest path to real-time donor visibility.
Frequently asked
What does the Givebutter MCP do in Switchy?
It connects your Givebutter nonprofit fundraising account so AI agents can create campaigns, manage donor contacts, retrieve transaction data, and set up webhooks for real-time donation notifications. You can automate donor outreach, generate fundraising reports, or sync campaign performance into other tools without switching between apps.
Do I need admin access to connect Givebutter?
You need an API key from your Givebutter account, which typically requires admin or owner permissions to generate. The key grants full read-write access to campaigns, contacts, funds, and webhooks, so only connect it if you're comfortable giving AI agents that level of control over your fundraising data.
Can the MCP send emails to donors or process payments?
No. It manages campaigns, contacts, and funds but doesn't send emails or charge credit cards directly. For donor communications, you'd export contact lists and use your email tool. Payment processing happens through Givebutter's hosted checkout pages, not via the MCP's 18 tools.
Why use this instead of logging into Givebutter directly?
Use the MCP when you want AI to pull fundraising metrics into reports, create campaigns from templates, or trigger actions based on donation webhooks. If you're just checking last night's donations or tweaking a campaign page, the Givebutter dashboard is faster. The MCP shines for repetitive tasks across multiple campaigns.
Who on the team should connect this integration?
Whoever manages your Givebutter account and understands which campaigns or contacts can be safely archived or deleted. The MCP includes destructive tools like Delete Campaign and Archive Contact, so the person connecting it should know your fundraising workflow well enough to avoid accidentally removing active data.