Givebutter MCP integration for AI agents.
Connect AI agents to Givebutter through 12 structured actions, including get campaign, get chapter, and get contact. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Givebutter integration exposes
The Givebutter Agent App exposes 12 provider-backed actions for finance work. Its current contract lets an authorized agent retrieve one givebutter campaign by id, retrieve one givebutter chapter by id, and retrieve one givebutter contact by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Givebutter account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Givebutter capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADRetrieve one Givebutter campaign by ID.
INPUTS: campaignId
get_chapterREADRetrieve one Givebutter chapter by ID.
INPUTS: chapterId
get_contactREADRetrieve one Givebutter contact by ID.
INPUTS: contactId
get_fundREADRetrieve one Givebutter fund by ID.
INPUTS: fundId
get_recurring_planREADRetrieve one Givebutter recurring plan by ID.
INPUTS: recurringPlanId
get_transactionREADRetrieve one Givebutter transaction by ID.
INPUTS: transactionId
list_campaignsREADList Givebutter campaigns with pagination and optional official filters.
INPUTS: page / perPage / query
list_chaptersREADList Givebutter chapters with pagination and optional official filters.
INPUTS: page / perPage / query
list_contactsREADList Givebutter contacts with pagination and optional official filters.
INPUTS: page / perPage / query
list_fundsREADList Givebutter funds with pagination and optional official filters.
INPUTS: page / perPage / query
list_recurring_plansREADList Givebutter recurring plans with pagination and optional official filters.
INPUTS: page / perPage / query
list_transactionsREADList Givebutter transactions with pagination and optional official filters.
INPUTS: page / perPage / query
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
campaignIdOPTIONAL- The Givebutter campaign ID.
get_chapter
chapterIdOPTIONAL- The Givebutter chapter ID.
get_contact
contactIdOPTIONAL- The Givebutter contact ID.
get_fund
fundIdOPTIONAL- The Givebutter fund ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Retrieve one Givebutter campaign by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaignVerify with Get Chapter
Retrieve one Givebutter chapter by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_chapterSAFETY BOUNDARY
Operate Givebutter with explicit limits
- Authorize Givebutter with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Givebutter data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Givebutter rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Givebutter task completed successfully.
CONNECTION MODEL
API key
Givebutter API key sent as a Bearer token in the Authorization header. Create and manage API keys in the Givebutter dashboard: https://dashboard.givebutter.com/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Givebutter.