Integration · MCP

GiveWP + MCP: let AI manage donation forms and read your giving data

Connect GiveWP to Claude, Cursor or ChatGPT through NibWP's MCP server. The AI creates and updates donation forms — levels, goals, copy — and reads donations, donors and stats, so campaign setup is a brief and reporting is a question.

Get the Bundle →See pricing
GiveWP + MCP: AI operating GiveWP through NibWP

Nonprofits and the agencies that serve them run GiveWP for one reason: forms that take donations reliably. Around that sit the jobs nobody has time for — a new campaign form every month, levels and goals to adjust, and a board that wants numbers. NibWP exposes GiveWP as typed MCP tools: list and read forms, donations and donors; create and update forms; ask for stats.

So a spring appeal is 'a form with €25/€50/€100/custom, a €10k goal, this copy, this thank-you' — planned, approved, created. And 'how much did we raise in Q2, by form, and how many first-time donors?' is answered from real data, read-only.

GiveWP is one of the 45+ integrations inside NibWP's WordPress MCP server — 3 typed GiveWP tools on top of 190+ WordPress tools. The full tool reference lives on the GiveWP integration page; this page is about what those tools let you do.

What AI can do in GiveWP

Create donation forms

Levels, suggested amounts, goals, copy and thank-you messages from a brief — reviewed before publish.

Update forms in bulk

Change levels, goals or copy across many forms at once — a matching campaign, a new minimum.

Giving stats

Totals by form, period or campaign; first-time versus returning donors — read-only.

Donors and donations

Read donor records and donation history to answer questions and find follow-ups.

Audits

Find forms with no goal, outdated copy or a broken thank-you page, and fix them in place.

Automation

Chain form creation, copy updates and reporting into a repeatable campaign workflow.

The GiveWP tools NibWP exposes

Every GiveWP capability is a typed MCP tool with a schema the AI client can read, so it calls the right thing with the right arguments instead of guessing at your database. Read tools are free to explore; write tools go through the approval flow.

  • nibwp/givewp-manage — Manage GiveWP donation forms, donations, and statistics.

Example prompts

Plain English is the interface. These are the kinds of requests agencies run against GiveWP every day:

  • “Create a 'Spring appeal' form with €25, €50, €100 and custom, a €10,000 goal and this intro copy.”
  • “How much did we raise in Q2 by form, and how many donors were first-time?”
  • “List every form without a goal set.”
  • “Which donations over €500 came in this month, and from whom?”
  • “Create a monthly giving form with €10/€20/€50 recurring levels.”

How it works with GiveWP

There is no new dashboard to learn. You describe an outcome, NibWP plans it, and you approve before anything is written.

  1. Connect — install NibWP, connect Claude, Cursor, ChatGPT or any MCP client. GiveWP is detected automatically and its tools appear in the client.
  2. Describe — tell it the campaign, the change or the question. NibWP reads existing forms and donation data first and shows the plan before creating anything.
  3. Approve — NibWP shows the plan: which records it will create or change, and what will stay untouched. Nothing happens until you say yes.
  4. Done — it writes real GiveWP data through the plugin's own APIs and reports back in plain English, with every change in the audit log.

Why not just a generic AI?

A general-purpose assistant can write text about GiveWP; it cannot safely operate it. The difference is structure, context and control.

A generic assistant

  • Writes appeal copy for you to paste into a form
  • Cannot see your forms, donations or donors
  • Cannot answer a single reporting question from real data

GiveWP + NibWP

  • Creates and updates real GiveWP forms with levels and goals
  • Reads donations and donors for real answers
  • Shows the plan first and logs every change

Safe by default

NibWP is built for agencies running client sites, so control and traceability come first:

  • Nothing is written without your approval — you see the plan first, and you can run in draft mode.
  • Every action is recorded in a full audit trail, per site and per user.
  • It runs on GiveWP's own functions and APIs — your data stays on your server, nothing is copied to a third-party service.
  • Donations and donors are read-only; refunds and deletions are never part of an ordinary connection.

Related integrations

Most sites pair GiveWP with other plugins NibWP already speaks: FluentCRM + MCP, Fluent Forms + MCP, Gravity Forms + MCP, WooCommerce + MCP, WPForms + MCP, WordPress + MCP. All of them ship in the same plugin — see pricing for what each plan includes.

FAQ

Questions, answered

Everything about running GiveWP with NibWP.

Does it need GiveWP installed?
Yes. Once GiveWP is active, NibWP detects it and its tools go live in your connected AI client — no configuration needed.
Can it create donation forms, not just read them?
Yes. Forms with levels, goals, copy and thank-you settings are created through GiveWP’s own layer and behave exactly as if built in the admin.
Can it refund or edit donations?
No. Donations and donors are readable so the agent can answer questions and flag follow-ups; money movement stays with you in GiveWP.
Is donor data safe?
It never leaves your server — NibWP runs on your site and reads through GiveWP’s API. Access is scoped per connection and every read and write is logged.
Do I need a Pro Skill?
No. The GiveWP integration works on Pro. Pro Skills are for design-to-build builder output.

Run campaigns by describing them.

Get the Bundle and let NibWP manage GiveWP forms and answer giving questions — with an approval step and an audit trail.

Get the Bundle →See pricing