Read and manage donors, donations, recurring gifts and tasks in your Funraise fundraising CRM.
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.
Try asking Muse: "Show me all donations from the last 24 hours and add a thank you note to the top donor's record."
Source: Found in the official MCP Registry (io.usefulapi/funraise) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://funraise.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Funraise MCP is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://funraise.usefulapi.io/mcpResponse time at the last check: 106ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
funraise_list_supportersList 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_supporterOne supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}.funraise_list_donationsList 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/dofunraise_get_donationOne donation by its Funraise id: amount, date, supporter, household, form, allocation, dedication, fees, UTM, subscription. GET /api/v1/crm/donation/{id}.funraise_list_subscriptionsList 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/subsfunraise_get_subscriptionOne recurring gift by id: status, frequency, amount, last and next payment date, cancel date, supporter. GET /api/v1/crm/subscription/{id}.funraise_list_formsList donation and event forms, filtered by type, status and version. Needs the CREATOR role on the key. GET /api/v1/form.funraise_list_campaign_sitesList 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_siteOne campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}.funraise_list_form_custom_questionsThe custom questions attached to a form. GET /api/v2/form/{formId}/custom-question.funraise_get_householdOne household: name, salutation, member count, primary contact, preferred address, total giving. GET /api/v1/household/{householdId}.funraise_get_household_memberThe household membership of a supporter (household and supporter details). GET /api/v1/household/member/{supporterId}.funraise_list_household_addressesAddresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address.funraise_list_supporter_addressesAddresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address.funraise_get_addressOne address by id (street, city, state, postal code, country, primary flag, household and supporter). GET /api/v1/address/{addressId}.funraise_list_supporter_notesNotes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note.funraise_list_household_notesNotes on a household's record (paginated). GET /api/v2/household/{id}/note.funraise_get_noteOne note by id, with title, body, importance and author. GET /api/v2/note/{id}.funraise_list_supporter_interactionsThe interaction log of a supporter (calls, emails, meetings): subject, description, action, assigned user, dates. GET /api/v1/interaction/donor/{donorId}.funraise_list_user_interactionsInteractions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}.funraise_get_interactionOne interaction by id. GET /api/v1/interaction/{id}.funraise_get_taskOne task by id: title, description, due date, status, assigned user, supporter, linked donation. GET /api/v2/task/{id}.funraise_create_supporter_noteWRITE: 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_noteWRITE: add a note to a household's record in Funraise. Creates a new note each call. POST /api/v2/household/{id}/note.funraise_create_interactionWRITE: log an interaction (call, email, meeting) on a supporter's record. Creates a new interaction each call. POST /api/v1/interaction.funraise_create_taskWRITE: 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_taskWRITE: 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_supporterWRITE: 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.https://funraise.usefulapi.io/mcpNot 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.
At the last check (October 29, 2026, 23:56 UTC) the endpoint was working, answering in 106ms. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 28 tools, including funraise_list_supporters, funraise_get_supporter, funraise_list_donations, funraise_get_donation. For example, you could ask Muse: "Show me all donations from the last 24 hours and add a thank you note to the top donor's record."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/funraise)). If you build Funraise MCP, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/funraise-mcp"><img src="https://musedirectory.ai/badge/funraise-mcp.svg" alt="Funraise MCP on musedirectory.ai" width="236" height="40"></a>