mcpbeat Sign in

Funraise MCP by usefulapi MCP Server

answering

Funraise MCP by usefulapi is answering right now. Last checked 13 min ago. It exposes 28 tools. Last commit 1 Nov 2026.

Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters.

Uptime history 7 days of history · worst day 98%
7 days agonow
100.0%
Uptime 24h
91 of 91 checks
28
Tools
read from the server
179 ms
Response time
average over 24h
1
Stars
last commit 1 Nov 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day
30 Oct a tool changed version2 times that day
29 Oct a tool changed version2 times that day
28 Oct a tool changed version2 times that day
27 Oct a tool changed version
and 6 more, back to 27 October 2026

Funraise MCP by usefulapi missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add funraise --transport http https://funraise.usefulapi.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://funraise.usefulapi.io/mcp
~/.codex/config.toml
[mcp_servers.funraise]
url = "https://funraise.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "funraise": {
      "url": "https://funraise.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "funraise": {
      "type": "http",
      "url": "https://funraise.usefulapi.io/mcp"
    }
  }
}

Available tools 28

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

funraise
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_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_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_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_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_get_address
One address by id (street, city, state, postal code, country, primary flag, household and supporter). GET /api/v1/address/{addressId}.
funraise_get_campaign_site
One campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}.
funraise_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_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}.
funraise_get_interaction
One interaction by id. GET /api/v1/interaction/{id}.
funraise_get_note
One note by id, with title, body, importance and author. GET /api/v2/note/{id}.
funraise_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_get_supporter
One supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}.
funraise_get_task
One task by id: title, description, due date, status, assigned user, supporter, linked donation. GET /api/v2/task/{id}.
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_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_list_form_custom_questions
The custom questions attached to a form. GET /api/v2/form/{formId}/custom-question.
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_household_addresses
Addresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address.
funraise_list_household_notes
Notes on a household's record (paginated). GET /api/v2/household/{id}/note.
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 = "Cancelled" order by id asc. GET /api/v1/crm/subscription.
funraise_list_supporter_addresses
Addresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address.
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_supporter_notes
Notes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note.
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_list_user_interactions
Interactions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}.

Endpoints

URLTransportStateLatencyChecked
https://funraise.usefulapi.io/mcp streamable-http answering 157 ms 13 min ago

Alternatives to Funraise MCP by usefulapi

same job, measured the same way
Givecloud MCP by usefulapi
by usefulapi

Read supporters, contributions, recurring donations, fundraising products and feed posts.

10 tools answering
GivingFuel MCP by usefulapi
by usefulapi

Read GivingFuel forms, donations, transactions, recurring gifts and donors; manage coupons.

15 tools answering
Gladly MCP by usefulapi
by usefulapi

Find customers, read conversations, items and tasks; add internal notes in Gladly.

16 tools answering
Raisely MCP by usefulapi
by usefulapi

Read campaigns, donations, profiles and supporters; record offline donations and upsert users.

23 tools answering
Qgiv MCP by usefulapi
by usefulapi

Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events.

21 tools answering
Bloomerang MCP by usefulapi
by usefulapi

Search Bloomerang constituents and donations; log interactions, notes and tasks.

20 tools answering
Tokeet MCP by usefulapi
by usefulapi

Read Tokeet rentals, rates, guests, tasks and expenses; add guests, notes and tasks.

24 tools answering
KashFlow MCP by usefulapi
by usefulapi

Read KashFlow invoices, customers, suppliers, banking and reports; add customers, notes.

38 tools answering

Funraise MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Funraise MCP by usefulapi do?
It exposes 28 tools, read directly from the server on our last check. Among them: funraise_complete_task, funraise_create_household_note, funraise_create_interaction, funraise_create_supporter, funraise_create_supporter_note, funraise_create_task and 22 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Funraise MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 179 ms. The bar chart above shows every period we have measured.
How do I connect Funraise MCP by usefulapi?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Funraise MCP by usefulapi need an API key?
No. Funraise MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 28 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Funraise MCP by usefulapi?
It answers our handshake in 179 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Funraise MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at funraise.usefulapi.io, which runs on its operator's own terms.