Funraise MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://funraise.usefulapi.io/mcp

claude mcp add --transport http funraise https://funraise.usefulapi.io/mcp

{
  "mcpServers": {
    "funraise": {
      "url": "https://funraise.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "funraise": {
      "type": "http",
      "url": "https://funraise.usefulapi.io/mcp"
    }
  }
}

https://funraise.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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 id of the previous page. GET /api/v1/crm/do

• 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_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/subs

• 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_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}.

• 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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 70 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 28 tool descriptions and found no hidden instructions to the AI

Compared with others in Docs, sheets & office worki

• More stars than 0% of the other 2167 servers in this category
• Published to the registry more recently than 97% of the other 2167 servers in this category
• Basic checks equal to or better than 100% of the other 2167 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{