Read supporters, contributions, recurring donations, fundraising products and feed posts. For fundraising teams using Givecloud for supporters and donations. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"givecloud": {
"url": "https://givecloud.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"givecloud": {
"type": "http",
"url": "https://givecloud.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Search supporters by name or email, then inspect a matching record and its contact and consent status.
givecloud_list_supporters givecloud_get_supporter
List contributions between UTC date boundaries and inspect an individual contribution’s amount, payment status and selected line items. Continue through result pages for the period.
givecloud_list_contributions givecloud_get_contribution
List recurring profiles and inspect their donation amounts, status and next billing dates without exposing payment instruments.
givecloud_list_recurring_profiles givecloud_get_recurring_profile
Find fundraising products by code or name, then review their prices, fundraising goals and reported progress.
givecloud_list_products givecloud_get_product
The login page asks for your Givecloud account and Givecloud personal access token.
Create a dedicated token in My Profile → Personal Access Tokens. Enter only the account label from account.givecloud.co; custom domains are not supported. API access must be enabled for your account. These tools only read data, but your token may allow broader actions: revoke it in Givecloud to disconnect. Requested donor identities, emails, donation amounts and other selected business data pass through UsefulAPI to your chosen AI client and model provider. Addresses, payment instruments, child/sponsorship records and arbitrary custom fields are omitted. Billing and usage are per account/token pair; rotating the token creates a separate identity. Independent integration, not an official Givecloud product.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Givecloud account and Givecloud personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Givecloud connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
givecloud_list_supporters | read | Search supporters Read one page of supporters, with name/email and consent status. Addresses, payment details, custom fields and groups are omitted. Name and email are partial filters. GET /admin/api/v2/supporters. |
givecloud_list_contributions | read | List contributions Read one page of contribution amounts, status, supporter identity and selected line items. Payment instruments, addresses, custom fields, comments and sponsored-child data are omitted. Date filters are exclusive and UTC. GET /admin/api/v3/contributions. |
givecloud_list_recurring_profiles | read | List recurring donation profiles Read one page of recurring donation amounts, schedules, status and supporter identity. Payment instruments and addresses are omitted. GET /admin/api/v3/recurring-profiles. |
givecloud_list_products | read | Search fundraising products Read one page of products, prices, goals and selected variants. code is exact; name is partial. GET /admin/api/v2/products. |
givecloud_list_posts | read | List feed posts Read one page of posts in a known feed. Obtain the feed ID in Givecloud; this connector does not enumerate feeds. name is partial. GET /admin/api/v2/feeds/{feedId}/posts. |
givecloud_get_supporter | read | Get a supporter Read one supporter by its Givecloud ID. Returns the same selected fields as the corresponding list tool. No business data is changed. |
givecloud_get_contribution | read | Get a contribution Read one contribution by its Givecloud ID. Returns the same selected fields as the corresponding list tool. No business data is changed. |
givecloud_get_recurring_profile | read | Get a recurring profile Read one recurring profile by its Givecloud ID. Returns the same selected fields as the corresponding list tool. No business data is changed. |
givecloud_get_product | read | Get a fundraising product Read one fundraising product by its Givecloud ID. Returns the same selected fields as the corresponding list tool. No business data is changed. |
givecloud_get_post | read | Get a feed post Read one feed post by its Givecloud ID. Returns the same selected fields as the corresponding list tool. A known feed_id is required. No business data is changed. |
givecloud_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
givecloud_request_feature | Request a missing feature Tell usefulapi that the user needs something the Givecloud tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
givecloud_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Givecloud (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
givecloud_cancel_subscription | Cancel the Pro subscription Cancel the caller's Givecloud Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run givecloud_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account/token pair | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Givecloud server only. Subscribe with givecloud_upgrade (it returns a Stripe Checkout link). Cancel any time with givecloud_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running givecloud_upgrade before then undoes the cancel. Or write to [email protected].
Find a supporter and review consent. Review contributions for a reporting period. Review recurring donation schedules. Compare fundraising product goals. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Givecloud. The server calls the Givecloud API with your own Givecloud access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Givecloud account and Givecloud personal access token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Givecloud account and Givecloud personal access token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Givecloud API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Givecloud.
All 10 Givecloud tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Givecloud server only. Cancel any time: Pro then runs to the end of the paid period. Run givecloud_usage_status to see how many calls you used.
Ask the AI to run givecloud_upgrade: it returns a Stripe Checkout link. To cancel, run givecloud_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with givecloud_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.