Daffy MCP integration for AI agents.
Connect AI agents to Daffy through 10 structured actions, including get balance, get current user, and get nonprofit. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 10
- 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 Daffy integration exposes
The Daffy Agent App exposes 10 provider-backed actions for finance work. Its current contract lets an authorized agent get the balance for the daffy account associated with the api key, get the daffy user associated with the api key, and get a daffy nonprofit by ein. 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 Daffy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Daffy capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_balanceREADGet the balance for the Daffy account associated with the API key.
get_current_userREADGet the Daffy user associated with the API key.
get_nonprofitREADGet a Daffy nonprofit by EIN.
INPUTS: ein
get_userREADGet a Daffy user by username.
INPUTS: username
get_user_donationREADGet a specific Daffy donation for a specific user.
INPUTS: userId / donationId
list_contributionsREADList contributions for the Daffy account associated with the API key.
INPUTS: page
list_donationsREADList donations for the Daffy account associated with the API key.
INPUTS: page
list_user_causesREADList causes associated with a Daffy user.
INPUTS: userId
list_user_donationsREADList Daffy donations for a specific user.
INPUTS: userId / page
search_nonprofitsREADSearch Daffy nonprofits with optional cause and pagination filters.
INPUTS: query / causeId / page
INPUT CONTRACTS
Know what the action needs before it runs.
get_nonprofit
einREQUIRED- The nonprofit EIN used by Daffy.
get_user
usernameREQUIRED- The Daffy username.
get_user_donation
userIdREQUIRED- The Daffy user identifier.
donationIdREQUIRED- The Daffy donation identifier.
list_contributions
pageOPTIONAL- The Daffy result page to request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Balance
Get the balance for the Daffy account associated with the API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_balanceVerify with Get Current User
Get the Daffy user associated with the API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Daffy with explicit limits
- Authorize Daffy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Daffy 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 Daffy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Daffy task completed successfully.
CONNECTION MODEL
API key
Daffy API key sent with the X-Api-Key header. Create or revoke API keys in the API subsection under your Daffy profile settings: https://www.daffy.org/settings/api
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
- 10
- 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 Daffy.