Givebutter for AI agents
Givebutter is a fundraising platform for nonprofits to run campaigns, sell tickets, and track donors. Nonprofit staff use it to manage donations and supporter relationships. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Givebutter.
Look up a donor's contact record
Pull a supporter's contact details and giving history before a follow-up thank-you message.
Create a new campaign
Set up a new fundraising campaign with a goal and description ready for the team to launch.
Delete a fund with confirmation
Remove an unused fund only after a staff member confirms no transactions are tied to it.
58 Givebutter actions, graded by risk.
Every Givebutter action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
27Look things up. Allowed by default.
- givebutter.get_fundGet Fund
- givebutter.get_plansGet Plans
- givebutter.get_teamsGet Teams
- givebutter.list_fundsList Funds
- givebutter.get_contactGet Contact
- givebutter.get_membersGet Members
- givebutter.get_payoutsGet Payouts
- givebutter.get_ticketsGet Tickets
- givebutter.get_webhookGet Webhook
- givebutter.get_campaignGet Campaign
- givebutter.get_webhooksGet Webhooks
- givebutter.list_pledgesList Pledges
- givebutter.get_householdGet Household
- givebutter.list_contactsList Contacts
- givebutter.list_messagesList Messages
- givebutter.list_campaignsList Campaigns
write
23Create and change things. Allow, or ask the user first.
- givebutter.create_fundCreate Fund
- givebutter.update_fundUpdate Fund
- givebutter.create_contactCreate Contact
- givebutter.create_webhookCreate Webhook
- givebutter.update_contactUpdate Contact
- givebutter.update_webhookUpdate Webhook
- givebutter.create_campaignCreate Campaign
- givebutter.update_campaignUpdate Campaign
- givebutter.add_contact_tagsAdd Contact Tags
- givebutter.create_householdCreate Household
- givebutter.update_householdUpdate Household
- givebutter.create_transactionCreate Transaction
- givebutter.update_contact_putUpdate Contact (PUT)
- givebutter.update_webhook_putUpdate Webhook (PUT)
- givebutter.update_campaign_putUpdate Campaign (PUT)
- givebutter.create_discount_codeCreate Discount Code
destructive
8Delete, cancel or archive. Ask first, or deny outright.
- givebutter.delete_fundDelete Fund
- givebutter.delete_webhookDelete Webhook
- givebutter.archive_contactArchive Contact
- givebutter.delete_campaignDelete Campaign
- givebutter.delete_householdDelete Household
- givebutter.remove_contact_tagsRemove Contact Tags
- givebutter.delete_discount_codeDelete Discount Code
- givebutter.delete_contact_activityDelete Contact Activity
Givebutter in three steps.
- 01Your users connect GivebutterThey add their Givebutter api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Fund” can wait for the user, and “delete Fund” can be denied outright.
- 03Any agent can actYour agent calls Givebutter through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('givebutter', { read: 'allow', write: 'ask', // create_fund destructive: 'deny', // delete_fund }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Givebutter connects.
Users add their Givebutter api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Givebutter connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Givebutter from any agent.
More finance and accounting apps.
Givebutter and Arc0, answered.
Can I use Givebutter with Claude, ChatGPT or Cursor?
Yes. Connect Givebutter to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Givebutter actions you allow.
How do users connect Givebutter?
Users add their Givebutter api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Givebutter actions can my agent take?
58 in total: 27 read, 23 write and 8 destructive, such as “create Fund”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Givebutter?
Yes. Actions like “delete Fund” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Givebutter too?
Yes. The same Givebutter connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Givebutter into your agent.
Your users connect Givebutter once, under your brand. Your agent gets 58 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan