Funraise MCP by usefulapi
Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters.
What it does
Funraise MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)Hosted endpoint
https://funraise.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http funraise-mcp-by-usefulapi https://funraise.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"funraise-mcp-by-usefulapi": {
"url": "https://funraise.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1h agoONLINE Funraise MCP by usefulapi answered an MCP connection on 25 Oct 2026 and introduced itself as funraise-mcp 1.0.0 (MCP protocol 2025-06-18).
28 tools offered to AI assistants
funraise_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· One supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}.funraise_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 idfunraise_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· 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 = "Cancellefunraise_get_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· 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· 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· One campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}.funraise_list_form_custom_questions· The custom questions attached to a form. GET /api/v2/form/{formId}/custom-question.funraise_get_household· One household: name, salutation, member count, primary contact, preferred address, total giving. GET /api/v1/household/{householdId}.funraise_get_household_member· The household membership of a supporter (household and supporter details). GET /api/v1/household/member/{supporterId}.
Show 16 more
funraise_list_household_addresses· Addresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address.funraise_list_supporter_addresses· Addresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address.funraise_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· Notes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note.funraise_list_household_notes· Notes on a household's record (paginated). GET /api/v2/household/{id}/note.funraise_get_note· One note by id, with title, body, importance and author. GET /api/v2/note/{id}.funraise_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· Interactions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}.funraise_get_interaction· One interaction by id. GET /api/v1/interaction/{id}.funraise_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'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's record in Funraise. Creates a new note each call. POST /api/v2/household/{id}/note.funraise_create_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 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: 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 (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.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://funraise.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Website | https://usefulapi.io/funraise/ | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 1h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1h ago |
Change history
- NEW25 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Funraise MCP by usefulapi still online?
Free alerts · no accountQuestions about Funraise MCP by usefulapi
How do I connect Funraise MCP by usefulapi?
Use the hosted endpoint https://funraise.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Funraise MCP by usefulapi offer?
When Electra Index connected on 25 Oct 2026, it listed 28 tools: funraise_list_supporters, funraise_get_supporter, funraise_list_donations, funraise_get_donation, funraise_list_subscriptions, funraise_get_subscription, funraise_list_forms, funraise_list_campaign_sites and more. The full list is in "Live check" above.
Is Funraise MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.