Read GivingFuel forms, donations, transactions, recurring gifts and donors; manage coupons. 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": {
"givingfuel": {
"url": "https://givingfuel.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"givingfuel": {
"type": "http",
"url": "https://givingfuel.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.
The login page asks for your GivingFuel API key.
Create it in your GivingFuel dashboard under Account settings → Integrations. The key gives access to your whole account's data (donor names, emails and addresses included), so only connect an AI assistant you trust. Your key is used only to call the GivingFuel API on your behalf; it is never shown to anyone.
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 GivingFuel API key. 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 GivingFuel connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
givingfuel_list_forms | read | List donation forms List the account's GivingFuel forms (donation / fundraising pages): id, name, status (open or closed), created and updated dates. Use the form ids to filter orders, transactions and subscriptions. GET /forms. |
givingfuel_get_form | read | Get donation form One form by id: name, status, accounting reference, time zone and its field layout. GET /forms/{id}. |
givingfuel_get_form_inventory | read | Get form inventory Inventory items of a form (limited-quantity items): path, name, sold and remaining quantity. GET /forms/{id}/inventory. |
givingfuel_list_orders | read | List donation orders List donation orders (one per checkout): order number, donor billing name and address, form, total, currency and status, newest or oldest first. Filter by form, status, donor email, customer id, order number or dates. GET /search/orders. |
givingfuel_get_order | read | Get donation order One order by id with the donor's billing details, form, totals and status. Set include_transactions to embed the payments (charges and refunds) of the order. GET /search/orders/{id}. |
givingfuel_list_transactions | read | List transactions List payment transactions (money movements): amount, deductible amount, currency, type (charge, refund, voucher), payment method, masked card, status, form and donor email. Filter by type, method, form, order, donor or dates. GET /search/transactions. |
givingfuel_get_transaction | read | Get transaction One transaction by id: amounts, type, payment method, masked card, gateway message and status. GET /search/transactions/{id}. |
givingfuel_list_subscriptions | read | List recurring gifts List recurring donations (subscriptions): amount, schedule, status, last and next payment date, payments remaining, form and donor email. Filter by form, status, donor, or next/last payment date. GET /search/subscriptions. |
givingfuel_get_subscription | read | Get recurring gift One recurring donation by id: amount, schedule, status, last and next payment, payments remaining. GET /search/subscriptions/{id}. |
givingfuel_list_customers | read | List donors List customer records (donors): id, email, billing name and address, lifetime amount, created and updated dates. Filter by email or dates. New donors can take up to 5 minutes to appear. GET /search/customers. |
givingfuel_get_customer | read | Get donor One donor (customer record) by id: email, billing details and total amount. GET /search/customers/{id}. |
givingfuel_list_coupons | read | List coupons List GivingFuel coupons: account-wide ones, or only those of one form when form_id is given. Shows discounts, codes, availability, redeemed count and expiry. GET /coupons/global or /coupons/forms/{id}. |
givingfuel_get_coupon | read | Get coupon One coupon by id with its discounts, codes, availability and redeemed counts. GET /coupons/{id}. |
givingfuel_create_coupon | write | Create coupon WRITE: create a discount coupon in the live GivingFuel account (it can be redeemed by donors right away). One discount (fixed amount or percent) and one or more codes; optionally limited to one form, to a number of uses, and to an expiry date. Not idempotent: calling it twice creates two coupons. POST /coupons. |
givingfuel_delete_coupon | write | Delete coupon WRITE: permanently delete a coupon from the live GivingFuel account; its codes stop working immediately and this cannot be undone. Show the coupon (givingfuel_get_coupon) and get the user's approval first, then call with confirm: true. GET /coupons/{id}, then DELETE /coupons/{id}. |
givingfuel_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. | |
givingfuel_request_feature | Request a missing feature Tell usefulapi that the user needs something the GivingFuel 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. | |
givingfuel_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on GivingFuel (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+, $19/month or $190/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. | |
givingfuel_cancel_subscription | Cancel the Pro subscription Cancel the caller's GivingFuel 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 givingfuel_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 user | $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 GivingFuel server only. Subscribe with givingfuel_upgrade (it returns a Stripe Checkout link). Cancel any time with givingfuel_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running givingfuel_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 GivingFuel. The server calls the GivingFuel API with your own GivingFuel 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 GivingFuel API key. 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 GivingFuel API key. 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 GivingFuel 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 GivingFuel.
Yes, if you approve it. 2 of the 15 GivingFuel tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
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 GivingFuel server only. Cancel any time: Pro then runs to the end of the paid period. Run givingfuel_usage_status to see how many calls you used.
Ask the AI to run givingfuel_upgrade: it returns a Stripe Checkout link. To cancel, run givingfuel_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 givingfuel_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.