MCP apps
Connect AI assistants to your Fundraise Up data with credentials that limit what each assistant can read.
AI assistants such as Claude, ChatGPT, and Salesforce Agentforce can read your Fundraise Up data through the Model Context Protocol (MCP). They connect in one of two ways:
- MCP server: Each person connects their own assistant and signs in with their Dashboard account. To turn on the MCP server and connect an assistant, see Fundraise Up MCP.
- MCP app: The AI assistant doesn’t sign in. Instead, an Organization Administrator creates an app in the Dashboard: a set of credentials for the assistant, together with the data and accounts it can read.
This article covers MCP apps.
When to use the MCP server or an MCP app
The choice depends on who uses the AI assistant and how much of your data it needs.
Use the MCP server when:
- People on your team want to ask their own assistant, such as Claude or ChatGPT, about your data.
- Each person should read only what their Dashboard role allows.
Use an app when:
- A platform connects without a person who signs in. Salesforce Agentforce, for example, can connect only through an app.
- An agency or a contractor needs part of your data, such as campaign results, without a Dashboard account.
- An AI assistant needs the same fixed set of data for everyone who uses it, such as Campaigns and Insights only.
- Supporter names and email addresses must stay out of an AI assistant.
For example, an agency reviews your campaigns. You can create an app that can read Campaigns and Insights, hide supporters' personal data, and give the agency the app credentials. When the work ends, remove the app, and the agency loses access.
The MCP server and apps work independently. When you turn off the MCP server, apps keep working.
How an app reads your data
An app reads with the permissions of an Organization Administrator, limited to the data and accounts selected in the app. Dashboard roles don’t apply. Everyone who uses an AI assistant connected to the app reads the same data, whatever their own role.
Access is read-only. An app can read your data, but it cannot create, change, or delete anything in your account.
When you edit an app, the changes apply from the next request the AI assistant sends, and the assistant doesn’t need to connect again. Tools you add are the exception: most assistants load the list of tools when a conversation starts, so start a new conversation to use them.
Each account can have up to 25 apps. Only Organization Administrators can create, edit, and remove them.
Step 1: Create an app
To create an app:
- Go to Settings > MCP.
- In the Apps section, click Connect app.
- In App name, enter a name that tells your team what the app is for, such as Agency or Agentforce. Each name must be unique in your account.
- To keep supporter details out of the AI assistant, select Hide supporters' personal data.
- Under Accounts, choose which subaccounts the app can read.
- Under Tool access, select the data the app can read. You must select at least one tool.
- Click Connect app.
- In the App connected window, copy the App server URL, the API key, the Client ID, and the Client secret. Your AI assistant needs either the API key or the client ID and secret. See “Which credentials to use” below for which one. The API key and the client secret appear only once, so copy them before you click Close. Keep them private: anyone who has them can read everything the app allows.
Which credentials to use
Every app comes with both an API key and a client ID and secret. Your AI assistant needs only one of them:
- Client ID and secret: Salesforce Agentforce. The assistant uses the client ID and secret to get access for 1 hour at a time and renews that access on its own.
- API key: Claude, Claude Code, Cursor, VS Code, Microsoft Copilot Studio, and Notion Custom Agents. The assistant sends the key with every request.
ChatGPT and Slackbot connect to MCP servers only through a sign-in page, so they can’t use an app. Connect them through the MCP server instead.
For an assistant that isn’t listed, check its MCP settings. If they accept a client ID and secret without a sign-in page, use the client ID and secret. If they let you add an API key or a request header, use the API key.
See “Step 2: Connect the AI assistant” below for where to enter the credentials in each assistant.
Personal data
Hide supporters' personal data replaces supporter names, email addresses, and supporter comments with asterisks.
Amounts, dates, and IDs stay visible. An assistant can still match a donation to its supporter and recurring plan, and it can still total or compare donations. Payment details, such as card brand and last 4 digits, stay visible as well.
Accounts
If your account has subaccounts, choose which of them the app can read:
- None: Only the account where you create the app.
- All subaccounts: Your account and every subaccount, including ones you add later.
- All subaccounts except selected: Your account and every subaccount except the ones you select. Subaccounts you add later are included.
- Selected subaccounts: Your account and only the subaccounts you select.
To create an app that reads one subaccount only, switch to that subaccount in the Dashboard and create the app there. Organization Administrators of the parent account can see, edit, and remove apps created in its subaccounts.
The MCP settings of a subaccount don’t limit apps of the parent account. A parent app that covers a subaccount can read its data, whatever the subaccount settings. To keep a subaccount out of a parent app, exclude the subaccount under Accounts in that app.
Tool access
A tool is one kind of request an assistant can make, such as a list of donations or the details of one donation. Tools are grouped by the data they read: Donations, Supporters, Recurring plans, Campaigns, and Insights. You can select a whole group or single tools inside it. Every app can also read your organization details and search your subaccounts.
Step 2: Connect the AI assistant
Enter the app server URL and the credentials you copied in Step 1 in your AI assistant. Find your assistant below.
Salesforce Agentforce
Agentforce connects with the client ID and secret.
Before you start, check that your Salesforce user has the Manage AI Agents permission and the permissions that your agent type requires. Without them, Salesforce won’t let you add an MCP server.
- In Salesforce Setup, enter Agentforce in the Quick Find box, then select Agentforce Registry.
- Click New.
- Enter a server name, such as Fundraise Up. Salesforce adds this name to every Fundraise Up tool in Agentforce Assets, so pick one your team recognizes. Add a short description, then paste the app server URL in the URL field.
- For the authentication method, select OAuth 2.0, then fill in the fields:
- Identity Provider URL: The App server URL from the App connected window in Step 1, with
/oauth/tokenadded to the end. For example, if the app server URL ishttps://mcp.fundraiseup.com/app/MA123456789, enterhttps://mcp.fundraiseup.com/app/MA123456789/oauth/token. - Client ID and Client Secret: The Client ID and Client secret you copied from the App connected window in Step 1.
- Identity Provider URL: The App server URL from the App connected window in Step 1, with
- Click Create and Continue.
- Salesforce lists the tools you selected in the app and asks you to allow the ones your agents can use. Select them, then click Allow and Continue.
- Save your changes.
The tools appear as agent actions in Agentforce Assets. Add them to your agent in Agentforce Builder.
Claude
Claude connects with the API key. The steps depend on your Claude plan.
Request headers in Claude are in beta and available to some organizations. If the Add custom connector dialog has no Request headers section, Claude can’t connect to the app yet. Use the MCP server instead.
Team and Enterprise plans
Only a Claude Owner can add a custom connector. As the Owner, add the app for your whole organization:
- In Claude, go to Organization settings > Connectors.
- Select Add, then Custom. If Claude asks for the connector type, choose Web.
- Enter a name and paste the app server URL.
- For Authentication, choose No sign-in.
- Open Request headers and select the
authorizationheader. In the value, enterBearer, then the API key, for exampleBearer fru_mcp_.... Mark the header as Required. - Click Add.
After the Owner adds the connector, each member connects to it: go to Customize > Connectors, find the connector with the Custom label, and click Connect.
Free, Pro, and Max plans
On these plans, you add the app to your own Claude account:
- In Claude, go to Customize > Connectors.
- Click Add custom connector.
- Enter a name and paste the app server URL.
- For Authentication, choose No sign-in.
- Open Request headers and select the
authorizationheader. In the value, enterBearer, then the API key, for exampleBearer fru_mcp_.... Mark the header as Required. - Click Add.
Claude Code
Claude Code connects with the API key. In your terminal, run this command with the values from the app:
1claude mcp add --transport http fundraise-up <APP_SERVER_URL> --header "Authorization: Bearer <API_KEY>"To use the app in all your projects, add --scope user to the command. To check the connection, run claude mcp list. The app shows as ✔ Connected.
Cursor
Cursor connects with the API key. Add the app to ~/.cursor/mcp.json:
1{
2 "mcpServers": {
3 "fundraise-up": {
4 "url": "<APP_SERVER_URL>",
5 "headers": {
6 "Authorization": "Bearer <API_KEY>"
7 }
8 }
9 }
10}To keep the key out of the file, store it in an environment variable and use "Bearer ${env:FUNDRAISE_UP_API_KEY}" as the value.
VS Code
VS Code connects with the API key. Add the app to .vscode/mcp.json in your project:
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "fundraise-up-api-key",
6 "description": "Fundraise Up API key",
7 "password": true
8 }
9 ],
10 "servers": {
11 "fundraise-up": {
12 "type": "http",
13 "url": "<APP_SERVER_URL>",
14 "headers": {
15 "Authorization": "Bearer ${input:fundraise-up-api-key}"
16 }
17 }
18 }
19}When the server starts for the first time, VS Code asks for the API key and stores it securely.
Microsoft Copilot Studio
Copilot Studio connects with the API key.
- Open your agent and go to the Tools page.
- Select Add a tool, then New tool.
- Select Model Context Protocol.
- Fill in Server name and Server description. In Server URL, paste the app server URL.
- For the authentication type, select API key. Set Type to Header and enter
Authorizationas the header name. - Select Create.
- In the Add tool window, select Create a new connection. When Copilot Studio asks for the key, enter
Bearer, then the API key. - Select Add to agent.
Notion Custom Agents
Notion Custom Agents connect with the API key. They are available on Notion Business and Enterprise plans. Before you start, a Notion workspace admin must turn on custom MCP servers. As the admin, go to Settings > Connections, open the Manage tab, and turn on Enable custom MCP servers.
- Open the settings of your Custom Agent.
- Go to Tools & Access.
- Click Add connection, then Custom MCP server.
- Paste the app server URL and enter a display name.
- In the authentication details, add the API key as a bearer token.
- Click Connect.
ChatGPT and Slackbot
ChatGPT and Slackbot connect to MCP servers only through a sign-in page, so they can’t use an app. Connect them through the MCP server instead.
Edit an app
To change an app:
- Go to Settings > MCP.
- In the Apps section, find the app and select Edit app.
- Change the settings, then click Save changes.
To find the app server URL or the client ID later, open Edit app. The client secret and the API key don’t appear there.
Remove an app
Remove an app to cut off an AI assistant, or to replace a client secret or API key that was lost or shared by mistake.
To remove an app:
- Go to Settings > MCP.
- In the Apps section, find the app and select Remove app.
- To confirm, click Remove app.
To connect the AI assistant again, create a new app and enter its credentials in the assistant.
Audit log
The Audit log records when an Organization Administrator creates, edits, or removes an app. Each record names the app. The client secret and the API key never appear in it.
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