Contact Form 7 is one of the plugins NIBWP turns into a set of typed, agent-callable tools. Agents understand Contact Form 7 and can safely operate on it at scale — something no generic AI can do. The moment Contact Form 7 is active on your site, NIBWP detects it, reads its data model, and exposes it over the same secure MCP endpoint as everything else — no exports, no SQL, no brittle glue scripts. An AI agent connected through NIBWP can then read and operate on Contact Form 7 data through schema-validated calls that are scoped to your token and recorded in the audit log.
That means the work you used to do by clicking through Contact Form 7’s admin — creating records, updating fields, fixing data across hundreds of items — becomes something you can describe in plain language and have an agent carry out, safely and in bulk.
Agents understand Contact Form 7 and can safely operate on it at scale — something no generic AI can do. Active plugin in, typed tools out — read and write Contact Form 7 through any connected MCP client, with scopes, draft-mode and an audit log keeping it safe.
Your forms layer, programmable
Connecting Contact Form 7 to your agents changes what is possible with it:
- Structured access — Read and write Contact Form 7 data through typed, schema-validated calls.
- Bulk operations — Apply changes across hundreds of records in one operation.
- Full management — Create, update and configure Contact Form 7 — not just read it.
- Dynamic data — Feed Contact Form 7 values into templates, query loops and other tools.
- Safe by default — Scoped tokens and draft-mode keep large edits under control.
- Zero glue code — No exports, no SQL, no brittle scripts — just protocol.
What it exposes
NIBWP turns Contact Form 7 into the following typed abilities. Read tools gather context; write tools make changes — always within your token’s scope.
| Ability | Type | What it does |
|---|---|---|
nibwp/cf7-info | read | Detect Contact Form 7, its version, how many forms exist, whether submissions are being stored, and which spam protections are configured (read-only). |
nibwp/cf7-forms | write | List, read, create, rename and duplicate Contact Form 7 forms, and get the shortcode for embedding one. |
nibwp/cf7-template | write | Read and replace the form-tag markup that defines a form’s fields and layout. |
nibwp/cf7-fields | read | The fields of a form as Contact Form 7 itself parses them — name, type, whether required, and any options (read-only). |
nibwp/cf7-mail | write | Read and change what a form sends on submit: recipient, sender, subject, body, headers and attachments, for both the main mail and the autoresponder. |
nibwp/cf7-messages | write | Read and change the messages a form shows: success, validation errors, spam refusal and the rest. |
nibwp/cf7-settings | write | Read and change a form’s additional settings — demo mode, skipping mail, subscribers only, and any custom directives. |
nibwp/cf7-submissions | write | List and read stored submissions through Flamingo, and mark them spam or not spam. |
nibwp/cf7-spam | read | Report what is protecting a form from spam: Akismet field mapping, reCAPTCHA or Turnstile configuration, and whether a form has any protection at… |
nibwp/cf7-delete | write | Permanently delete a form or a stored submission. |
From hours to one prompt
Ask in plain language and the Contact Form 7 integration turns it into a couple of typed calls — no exports, no SQL, no plugin spelunking.
nibwp/cf7-forms (run)
✓ applied · 3 tools · 2.1sYou describe the outcome; the agent chooses the right tools, validates each call, and reports what it did. What used to be an afternoon of repetitive admin becomes a single instruction.
What you can build
A few of the things teams do with the Contact Form 7 integration:
Bulk backfills
Populate or update a field across an entire dataset at once.
Content generation
Have an agent draft and fill structured Contact Form 7 data from a brief.
Audits
Find empty or inconsistent records and fix them in place.
Automation
Chain Contact Form 7 actions into multi-step agent workflows.
How it stays safe
Capability without control is a liability, so NIBWP wraps every Contact Form 7 call in the same safety model as the rest of the platform:
- Scoped tokens — grant read-only or write access per agent, and revoke any token independently.
- Draft-mode — keep force-draft on so writes land as drafts you approve before they go live.
- Rate limits — per-token throttling stops a runaway loop from hammering your database.
- Audit log — every call is recorded with status, timing, the calling token and the result.
Getting started
Three steps to put the Contact Form 7 integration to work:
- Activate Contact Form 7 — NIBWP only exposes plugins that are active, and detects it automatically.
- Connect an MCP client — Claude, Cursor or your own code, using a scoped application-password token. See the overview.
- Describe the work — ask the agent what you want; it picks the right Contact Form 7 tools and carries it out under your review.
FAQ
Does it work with Contact Form 7?
Can it write, not just read?
Is bulk writing safe?
Do I need a Pro Skill?
Connect Contact Form 7
Activate the plugin, connect an MCP client, and let agents operate it safely.
Browse integrations