Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"funraise": {
"url": "https://funraise.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"funraise": {
"type": "http",
"url": "https://funraise.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Funraise API key.
Create it in Funraise under Settings → API Keys (the API is included in paid plans; the base plan allows 3,000 requests a month). Your key is used only to call the Funraise API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Funraise API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Funraise connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
funraise_list_supporters | read | List supporters List supporters (donors) in the Funraise CRM, newest first as Funraise returns them. Filter by exact email or by records changed in the last N hours. GET /api/v1/crm/supporter. |
funraise_get_supporter | read | Get supporter One supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}. |
funraise_list_donations | read | List donations List donations (transactions) with amount, date, supporter, form, campaign page, allocation, fees and tags. Filter by an exact transactionId, by last N hours, or by a lastUpdated timestamp; use last_id to continue from the last donation id of the previous page. GET /api/v1/crm/donation. |
funraise_get_donation | read | Get donation One donation by its Funraise id: amount, date, supporter, household, form, allocation, dedication, fees, UTM, subscription. GET /api/v1/crm/donation/{id}. |
funraise_list_subscriptions | read | List recurring subscriptions List recurring gifts (subscriptions) with status, frequency, amount, next payment date and supporter. The q filter is a Funraise expression (Funraise requires it; default: id > 0 order by id asc), for example: id > 10 and status = "Cancelled" order by id asc. GET /api/v1/crm/subscription. |
funraise_get_subscription | read | Get recurring subscription One recurring gift by id: status, frequency, amount, last and next payment date, cancel date, supporter. GET /api/v1/crm/subscription/{id}. |
funraise_list_forms | read | List forms List donation and event forms, filtered by type, status and version. Needs the CREATOR role on the key. GET /api/v1/form. |
funraise_list_campaign_sites | read | List campaign sites List campaign sites (fundraising pages), active by default or archived. Returns campaignSites with totalPageCount and totalRowCount. GET /api/v1/campaignSite/active or /archived. |
funraise_get_campaign_site | read | Get campaign site One campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}. |
funraise_list_form_custom_questions | read | List form custom questions The custom questions attached to a form. GET /api/v2/form/{formId}/custom-question. |
funraise_get_household | read | Get household One household: name, salutation, member count, primary contact, preferred address, total giving. GET /api/v1/household/{householdId}. |
funraise_get_household_member | read | Get household of a supporter The household membership of a supporter (household and supporter details). GET /api/v1/household/member/{supporterId}. |
funraise_list_household_addresses | read | List household addresses Addresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address. |
funraise_list_supporter_addresses | read | List supporter addresses Addresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address. |
funraise_get_address | read | Get address One address by id (street, city, state, postal code, country, primary flag, household and supporter). GET /api/v1/address/{addressId}. |
funraise_list_supporter_notes | read | List supporter notes Notes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note. |
funraise_list_household_notes | read | List household notes Notes on a household's record (paginated). GET /api/v2/household/{id}/note. |
funraise_get_note | read | Get note One note by id, with title, body, importance and author. GET /api/v2/note/{id}. |
funraise_list_supporter_interactions | read | List supporter interactions The interaction log of a supporter (calls, emails, meetings): subject, description, action, assigned user, dates. GET /api/v1/interaction/donor/{donorId}. |
funraise_list_user_interactions | read | List interactions assigned to a user Interactions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}. |
funraise_get_interaction | read | Get interaction One interaction by id. GET /api/v1/interaction/{id}. |
funraise_get_task | read | Get task One task by id: title, description, due date, status, assigned user, supporter, linked donation. GET /api/v2/task/{id}. |
funraise_create_supporter_note | write | Add a note to a supporter WRITE: add a note to a supporter's record in Funraise. Creates a new note each call. POST /api/v2/supporter/{id}/note. |
funraise_create_household_note | write | Add a note to a household WRITE: add a note to a household's record in Funraise. Creates a new note each call. POST /api/v2/household/{id}/note. |
funraise_create_interaction | write | Log an interaction WRITE: log an interaction (call, email, meeting) on a supporter's record. Creates a new interaction each call. POST /api/v1/interaction. |
funraise_create_task | write | Create a task WRITE: create a task in Funraise, linked to a supporter or to a donation (give at least one). Title is 40 characters at most. Creates a new task each call. POST /api/v2/task. |
funraise_complete_task | write | Complete a task WRITE: mark a task complete (sets the completed date to now; Funraise may also log an interaction if the task automation says so). PUT /api/v1/task/{id}/complete. |
funraise_create_supporter | write | Create a supporter WRITE: create a supporter (donor) record in Funraise. Creates a new record each call, so search with funraise_list_supporters (email) first to avoid duplicates. POST /api/v1/crm/supporter. |
funraise_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
funraise_request_feature | Request a missing feature Tell usefulapi that the user needs something the Funraise tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
funraise_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Funraise (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
funraise_cancel_subscription | Cancel the Pro subscription Cancel the caller's Funraise Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run funraise_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper API key | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Funraise server only. Subscribe with funraise_upgrade (it returns a Stripe Checkout link). Cancel any time with funraise_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running funraise_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Funraise. The server calls the Funraise API with your own Funraise access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Funraise API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Funraise API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Funraise API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Funraise.
Yes, if you approve it. 6 of the 28 Funraise tools can create or change data. The other 22 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Funraise server only. Cancel any time: Pro then runs to the end of the paid period. Run funraise_usage_status to see how many calls you used.
Ask the AI to run funraise_upgrade: it returns a Stripe Checkout link. To cancel, run funraise_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with funraise_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.