Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events. Hosted by usefulapi — connect from Claude, 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": {
"qgiv": {
"url": "https://qgiv.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"qgiv": {
"type": "http",
"url": "https://qgiv.usefulapi.io/mcp"
}
}
}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.
The login page asks for your Qgiv API token.
In Qgiv open Data Tools > API Access > Create API Token and select the forms it may read. The token is used only to call the Qgiv API on your behalf; it is never shown to anyone. Donor contact details are returned only when you ask for them.
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 Qgiv API 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.
| Tool | Type | What it does |
|---|---|---|
qgiv_list_recent_transactions | read | List recent transactions The most recent donations/transactions (newest first as Qgiv returns them): id, status, date, amount, fee, net, donor name and id, form, recurring link, payment type and last four card digits, fund. Donor contact details are left out unless include_contact is set; full card numbers are never returned. POST /reporting/transactions/last/{limit}. |
qgiv_list_transactions_by_date | read | List transactions by date range Transactions between two dates (inclusive), at most 31 days per call, paged with offset/limit. Same fields as qgiv_list_recent_transactions. Qgiv has no server-side paging, so a busy range is fetched whole and sliced; use a shorter range if it is too large. POST /reporting/transactions/dates/{begin}:{end}. |
qgiv_list_transactions_after_id | read | List transactions after an id Transactions with an id greater than the given one, sorted by id ascending and paged with limit; next_after_id is the cursor for the next call (use it as after_id). Handy for syncing new gifts. POST /reporting/transactions/after/{id}. |
qgiv_get_transaction | read | Get transaction One transaction in full: donation lines, fund/restriction, dedication, custom-field answers, event packages, registrations, refunds. Contact details only with include_contact; card data is reduced to the last four digits. POST /reporting/transactions/{id}. |
qgiv_list_recent_refunds | read | List recent refunds The most recent refunds (read-only): id, original transaction, refund and settle dates, amount, payment type, last four digits, fund. POST /reporting/refunds/last/{limit}. |
qgiv_list_refunds_by_date | read | List refunds by date range Refunds between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/refunds/dates/{begin}:{end}. |
qgiv_get_refund | read | Get refund One refund in full by id (read-only; this server never issues refunds). POST /reporting/refunds/{id}. |
qgiv_list_recurring_schedules | read | List recurring gift schedules Recurring donation schedules (read-only): id, start/end date, next billing date, frequency, amount, state, donor name and id, plus Qgiv's 12-month forecast. Filter by status active, paused, expired or deleted. Paged with offset/limit. POST /reporting/recurring/list or /reporting/recurring/{status}. |
qgiv_get_recurring_schedule | read | Get recurring gift schedule One recurring donation schedule by id (read-only; schedules cannot be changed here). POST /reporting/recurring/{id}. |
qgiv_list_statements | read | List statements Monthly fee/payout statements: id, date, amount contributed, fees, refunded, debited, credited and the summary totals (without the per-transaction rows; use qgiv_get_statement for those). Paged with offset/limit. POST /reporting/statements/list. |
qgiv_get_latest_statements | read | Get latest statements The latest statement(s) for the organization or form, with summary totals (per-transaction rows left out). POST /reporting/statements/latest. |
qgiv_get_statement | read | Get statement One statement by id with its transaction rows (first 100 shown; donor names only). POST /reporting/statements/{id}. |
qgiv_list_recent_registrations | read | List recent P2P registrations The most recent peer-to-peer (Hobnob) event registrations: id, category, registrant name, team, fundraising goal and amount raised. Contact details only with include_contact. POST /reporting/registrations/last/{limit}. |
qgiv_list_registrations_by_date | read | List P2P registrations by date range Peer-to-peer registrations between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/registrations/dates/{begin}:{end}. |
qgiv_get_registration | read | Get P2P registration One peer-to-peer registration in full (purchase history, team, totals, child registrations). Contact details only with include_contact. POST /reporting/registrations/{id}. |
qgiv_list_events | read | List events Events (ticketed/auction events) on the forms the token covers: id, dates and the top-level settings. Set include_details for packages, questions and promo codes. Notification e-mail addresses are never returned. POST /events/list. |
qgiv_list_pledges | read | List pledge options Pledge options configured on the form(s) (title, value, frequency, begin date, iterations, state), not donors' pledge records. POST /pledges/list. |
qgiv_get_pledge | read | Get pledge option One pledge option by id. POST /pledges/{id} (no package is sent, so nothing is changed). |
qgiv_list_custom_fields | read | List custom fields Custom (additional-question) fields configured on the form(s): id, reference, title, input type, required flags, display flags. POST /customFields/list. |
qgiv_list_report_mappings | read | List report mappings Report mappings (accounting export mappings) on the form(s): id, identifier, mapping data, export service, type. POST /reporting/mappings/list. |
qgiv_get_report_mapping | read | Get report mapping One report mapping by id. POST /reporting/mappings/{id}. |
qgiv_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
qgiv_request_feature | Request a missing feature Tell usefulapi that the user needs something the Qgiv 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. | |
qgiv_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Qgiv tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
qgiv_cancel_subscription | Cancel the Pro subscription Cancel the caller's Qgiv Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run qgiv_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this Qgiv server only. Subscribe with qgiv_upgrade (it returns a Stripe Checkout link). Cancel any time with qgiv_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running qgiv_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Qgiv. The server calls the Qgiv API with your own Qgiv access, so it sees only the data that your account can see.
The login page asks for your Qgiv API token. See Before you connect for where to find it.
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 Qgiv API 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 Qgiv 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 Qgiv.
All 21 Qgiv tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Qgiv server only. Run qgiv_usage_status to see how many calls you used.
Ask the AI to run qgiv_upgrade: it returns a Stripe Checkout link. To cancel, run qgiv_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 qgiv_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, 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.