Claude Givebutter connectorWhat Claude can do in your Givebutter account.
The Claude Givebutter connector exposes 5 tools. 4 read, 0 write, 1 is undocumented. Claude queries your live donations, contacts and campaigns and answers with real numbers. Here: what it can look up, what Givebutter keeps out of reach, and who can turn it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your development team
Pulling a fundraising number usually means an export, a spreadsheet and a pivot table. With the connector plugged in, you ask Claude the question the way the board would ask it, and Claude turns it into a query against your Givebutter account, runs it and answers with the actual figures.
Board update in one question. Ahead of the quarterly meeting, a development director asks how much the spring appeal raised. givebutter_query runs a filtered, aggregated query on your transactions and Claude replies with the total.
Know who your loyal donors are. Before a stewardship call, ask for this year's top recurring donors. Claude first uses givebutter_load_entity_context to see which contact fields it can filter and group, then builds the query.
Answer the how-to question on the spot. A volunteer wants to know how to set up a peer-to-peer page. givebutter_help_center searches Givebutter's help centre and Claude summarises the article.
What it cannot do: Givebutter states that the connector only reads and can never create, edit or delete anything in your account. Claude will not issue a refund, update a donor record or launch a campaign. It also does not run on its own: it will not thank a new donor when a gift lands. That kind of routine is the job of an automation tool, a different line of work covered on our Integrations page. If your campaign plan lives in a project board, the Claude asana connector can work alongside this one.
The vocabulary in one minute
Five words you will meet while connecting Givebutter.
- Connector
- The link you set up once between Claude and an account you already run, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude chooses the tools it needs by itself; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand over the access Claude uses afterwards. Granted once per person and revocable.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service like Givebutter.
Plug Givebutter into Claude in three steps
- 01
Find Givebutter in Claude
In Claude's settings, open Customize, then Connectors, and look for Givebutter. On a Team or Enterprise workspace, an Owner or Primary Owner must enable the connector before members can each sign in with their own account.
- 02
Start the connection
Click Connect on its row, then sign in to Givebutter in the window Givebutter opens. If you manage several Givebutter accounts, you pick the single one this connector will use. If the link breaks, Disconnect and reconnect.
- 03
Read the authorization screen
Read Givebutter's authorization screen before approving. It belongs to Givebutter, not to Claude, and it sets what the access covers. That access can also be withdrawn later from the Givebutter side.
The 5 tools, sorted by what they do
Givebutter gives Claude 5 tools: 4 that read your account, 0 that change something in it, and 1 no official source describes.
Four tools read your account or Givebutter's help content; one is named on the directory sheet and described nowhere. Tool names stay in English, exactly as Claude shows them.
- 4 read
- 1 not documented
What Claude reads (4)
4 toolsFour read-only tools. Givebutter says none of them can change your account.
givebutter_help_center
Searches Givebutter's own help centre for how-to answers, so Claude can explain a feature in its own words instead of leaving you to hunt for the right page yourself.
givebutter_load_entity_context
Before querying, Claude checks which fields exist for a type of data, contacts or transactions for example, so the query that follows asks for fields that are really there.
givebutter_query
This is the workhorse: one filtered query on one type of data, with optional sums, averages, counts and groupings, returning rows or just totals.
givebutter_who_am_i
Confirms which Givebutter account the connector is scoped to, so Claude knows whose donors and campaigns it is about to read before it answers anything.
Undocumented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and this page will not guess from the name.
givebutter_widget_helper
The directory sheet lists this name, and that is all we know. Givebutter's list of available tools leaves it out, and no Claude page mentions it, so this page will not describe it.
What Claude asks before acting
By default, Claude stops and asks for your confirmation before each action it takes on an account for you. The four documented Givebutter tools only read, so the rule has no write of theirs to stop.
On Team and Enterprise, workspace owners choose whether members can let some actions pass without being asked each time, and they can narrow what a connector may do for the whole organisation. Nobody bypasses that from their own account. Claude also uses your rights and nothing beyond: Givebutter says the connector can only reach what your connected account can see, in the one account you picked at sign-in.
Which plans include it
Of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere, which is a real hole in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. Givebutter adds that members who are not allowed to enable connectors see Request instead of Connect, which sends it to an admin. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing happens by itself when a donation arrives or a campaign closes.
By default the sheet only exposes reads, and Givebutter confirms it in its own documentation. Even so, a public tool list is an observed floor rather than a guarantee. The directory's partner badge is not a security audit, and Anthropic states on every sheet that it does not pick the tools a publisher exposes. All the detail on this page comes from Givebutter's documentation; neither Claude's help centre nor Anthropic's developer docs cover this connector.
Need help connecting Givebutter to Claude?
A person reads every message.
