Fundraise Up MCP
Connect AI assistants to your Fundraise Up data with the Model Context Protocol.
The Model Context Protocol (MCP) lets an AI assistant — an app like Claude or ChatGPT — read your Fundraise Up data. Connect an assistant, then ask about your account in plain language — the assistant reads the answer straight from Fundraise Up, so you do not export data or build on the API to get it.
Access is read-only. An assistant can read your data through MCP, but it cannot create, change, or delete anything in your account.
You manage MCP from Settings > MCP in your Dashboard. MCP is off until an Organization Administrator turns it on, and only Organization Administrators can enable or disable it.
Data an assistant can read
Once MCP is on, an assistant can read the data below.
| Data | What an assistant can read | Access |
|---|---|---|
| Donations | Your donations, filtered the way the Donations page filters them: by date, campaign, designation, supporter, source, payment method, status, and frequency. Each donation shows its amount, date, status, frequency, supporter, campaign, designation, and source. A single donation also shows the payment method, covered fees, the recurring plan it belongs to, and any comment the supporter left. | Read only |
| Recurring plans | Your recurring plans, filtered by date, status, campaign, designation, source, element, payment method, and amount. Each plan shows its status, amount, frequency, supporter, campaign, and next charge date. A single plan also shows the payment method, how many payments have succeeded, and the total collected so far. | Read only |
| Recurring plan totals | Active, new, reactivated, and canceled plans for a period, with the amount your active plans are expected to bring in each month. An assistant can compare one period against another. | Read only |
| Fundraising totals | Your total raised for a period, split into one-time donations and the first payment of new recurring plan, each with a total amount and a donation count. | Read only |
| Supporters | Your supporters, ranked by how much or how often they have given, and filtered by the date of a first donation or by whether a supporter has an active recurring plan. Each supporter shows a name, email address, lifetime total, and donation count. A single supporter also shows first and last donation dates, active recurring plans, and the campaigns they have given to. | Read only |
| Supporter totals | New, returning, and active supporters for a period, with the option to compare against another period. | Read only |
| Campaigns | A specific campaign, or a list of campaigns matching a name or code you search for. A campaign shows its status, the frequencies it offers, the designations attached to it, and the address of its Campaign Page. | Read only |
| Designations | A list of designations matching a name or code you search for. | Read only |
| Subaccounts | A list of your subaccounts. | Read only |
| Account information | Your organization's name, currency, and other account details. | Read only |
| AI tool performance | Results for each Fundraise Up AI tool you use: Upsell, Adaptive Cost Coverage, Abandoned Donation Recovery, Saved Recurring, and fraud prevention. | Read only |
| Insights | The figures behind the Insights page: • totals over time by day, week, or month; • breakdowns by country, device, frequency, payment method, designation, and tribute; • results by page address and UTM parameter; • results by element and by P2P fundraiser; • recurring retention by cohort; donations by day of the week and hour; • donations raised through AI assistants. | Read only |
An assistant can read a data type only when your Dashboard role has the read permission listed for it. If your role cannot see something in the Dashboard, the assistant cannot read it either.
Supporter names and email addresses appear in the donations, recurring plans, and supporter records that an assistant reads.
Requests are limited for each organization. If an assistant sends too many requests in a short time, its requests fail until the limit resets.
Step 1. Enable MCP
Turn on MCP before you connect an assistant.
- Go to Settings > MCP.
- Click Enable MCP server.
Your Server URL now appears in the section. Each organization has its own Server URL — copy it, since an assistant needs it to connect in Step 2.
Step 2. Connect an assistant
You connect an assistant once, using the Server URL from Step 1. After that, you can ask it about your Fundraise Up data in an ordinary conversation.
Every assistant sends you to a Fundraise Up sign-in first, though the exact steps to reach it depend on the assistant. After you sign in, Fundraise Up shows a screen that names the assistant and confirms that access is read-only. Approve it to finish, or decline to stop.
Connect Claude
On a Team or Enterprise plan, an Owner adds the connector for the organization first, then each person connects their own account.
- In Claude, go to Settings > Connectors.
- Click Add custom connector.
- Paste your Server URL, then click Add.
- Click Connect, sign in to Fundraise Up, and approve read-only access.
To use it in a chat, click the + below the message box and turn on the connector.
Connect ChatGPT
Custom connectors in ChatGPT need a paid plan. On a Business or Enterprise workspace, an admin turns on custom connectors (apps) first.
- In ChatGPT, go to Settings > Apps.
- Select Add custom app, then paste your Server URL.
- Sign in to Fundraise Up and approve read-only access.
To use it in a chat, click the + button or the Tools menu, select Fundraise Up MCP, and grant any permissions it requests.
Supported assistants
MCP works with MCP-compatible assistants. Fundraise Up supports:
- Claude, on the web and in the desktop app
- ChatGPT
- Notion AI
- Local assistants that run on your computer, such as Claude Code and custom agents.
Assistants that are not on this list might not be able to connect.
One organization per connection
When you connect an assistant, it works with the organization you had open in the Dashboard at the time. To use an assistant with another organization, switch to it in the Dashboard and connect again. Other people in your organization can connect their own assistants the same way.
Connection length
A connection stays active for 24 hours. Each request the assistant makes extends it by another 24 hours. After 24 hours with no requests, the connection ends and the assistant must connect again.
Disable MCP
Turn off MCP to cut off every connected assistant at once.
- Go to Settings > MCP.
- Click the three-dots (…) menu, then select Disable MCP server.
- In the Disable MCP server? dialog, click Disable MCP.
All connected assistants lose access right away and stop working. To turn MCP back on, click Enable MCP server again.
Turning MCP off is the way to revoke access, and it affects every connected assistant. You cannot disconnect a single assistant on its own.
Audit log
The Audit log records when an assistant is granted or declined access to your account. Each entry shows what happened, who authorized it, and when.
What you can ask
An assistant is most useful when it combines figures from across your account — summarizing, comparing, or drafting from them.
Once an assistant is connected, try one of these questions. If you get an answer back, the connection is working:
- Give me a quick summary of our fundraising.
- What is our total raised, and how does it split between one-time and recurring donations?
- Are we adding recurring plans faster than we are losing them?
- Who are our top 10 supporters by lifetime giving?
- Which countries did our donations come from last quarter?
- How are our Fundraise Up AI tools performing?
- Draft a board update summarizing our recurring giving.
Ready to elevate your fundraising efforts?
Connect with our sales team to explore how our innovative tools can transform your online giving experience.
Request a demo