# Funraise MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Funraise MCP

Read and manage donors, donations, recurring gifts and tasks in your Funraise fundraising CRM.

- Record: https://musedirectory.ai/connector/funraise-mcp
- Category: Finance & Bills
- Developer: usefulapi (https://usefulapi.io/funraise/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 106ms, checked 2026-10-29T23:56:16Z
- Endpoint: https://funraise.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T23:56:16Z)
- Source: Found in the official MCP Registry (io.usefulapi/funraise) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ffunraise

Connect to Funraise to view supporters, donations, recurring gifts and forms. Add notes, tasks and interactions to donor records. Create new supporters and manage your fundraising data.

Example request: "Show me all donations from the last 24 hours and add a thank you note to the top donor's record."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Funraise MCP to help me. It is a free service with an MCP server at https://funraise.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.

Screening checks:
- MCP handshake: pass (Answered in 106ms)
- Domain against threat feeds (Cloudflare security DNS): pass (funraise.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (28 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)