By Fahad Murtaza · Published · Updated
Read and triage your WordPress form submissions with an AI agent
WP MCP speaks the form builders most WordPress sites run, each through that plugin’s own API.
Free:
- Contact Form 7 (
contactform7-read/-write): forms, fields, mail templates, and, with Flamingo active, stored submissions - Forminator, SureForms and MetForm (
forminator-read,sureforms-read,metform-readand their write halves): forms and entries
Pro forms pack:
- Gravity Forms, WPForms, Formidable Forms, Ninja Forms and Fluent Forms: forms, fields, notifications, entries, and entry status; opt-in notification and confirmation edits on Gravity Forms, WPForms and Formidable; opt-in entry deletes on all but WPForms
What you need
- WP MCP installed and connected to your AI client (see the WordPress MCP plugin guide).
- One or more form plugins active. Each pair registers only while its plugin is loaded, so nothing is offered on a site that does not run it.
Inventory your forms
› List my Gravity Forms forms with their entry counts.
› Who gets emailed when the WPForms Contact form is submitted?
› Show me the mail template for my Contact Form 7 contact form.
Triage submissions
› Go through the last 20 entries on the Quote Request form, group them by what
people asked for, and flag anything urgent.
The agent pages through list-entries (page_size and offset) and reads
single ones with get-entry. Entry reads sit behind manage_options (on
Contact Form 7, edit_users, which is what Flamingo itself requires), because
submissions are personal data.
Clean up, reversibly
› Mark the obvious spam on the Contact form as spam.
update-entry-status moves an entry between the states its plugin has:
active, spam and trash on Gravity Forms and WPForms; active and trash on Ninja
Forms; unread, read, spam and trashed on Fluent Forms; inbox and trash on
Contact Form 7 with Flamingo. Every one is snapshotted first, so
rollback-operation restores it. Formidable has no spam or trash state, so it
has no status write.
Deletes, stated plainly
Contact Form 7 (Flamingo) and MetForm entries are posts, so their
delete-entry is snapshotted and can be restored at the original id.
On the Pro pack, Gravity Forms, Formidable and Fluent Forms deletes snapshot
every table row they remove, so rollback-session restores them, and a Ninja
Forms delete comes back with rollback-operation. All four are off until the
site opts in with the wpmcp_enable_forms_write filter, need confirm: true,
and (except Ninja Forms) refuse an entry with a payment record. WPForms offers
no delete.
Forminator and SureForms keep entries in tables WP MCP cannot snapshot, so their
delete-entry is off by default, needs confirm: true, and answers
recoverable: false: it is permanent. A reversible delete is not a GDPR
erasure either, because a copy stays in the snapshot history until it is pruned.
Common questions
Which WordPress form plugins can an AI agent read through WP MCP?
The free plugin covers Contact Form 7 (with Flamingo for stored submissions), Forminator, SureForms and MetForm. The Pro forms pack adds Gravity Forms, WPForms, Formidable Forms, Ninja Forms and Fluent Forms.
Can an AI agent read my form entries?
Yes. It pages through entries with list-entries (page_size and offset) and reads one with get-entry. Entry reads require manage_options, or edit_users on Contact Form 7 because Flamingo requires it, since submissions are personal data.
Can the agent mark form submissions as spam, and can I undo it?
Yes. update-entry-status moves an entry between the states its plugin supports, and each change is snapshotted so rollback-operation restores it. Formidable has no spam or trash state, so it has no status write.
Are deleted form entries recoverable?
It depends on the plugin. Contact Form 7 (Flamingo) and MetForm entries are posts, so a delete is snapshotted and restorable. On the Pro pack, Gravity Forms, Formidable, Ninja Forms and Fluent Forms deletes are opt-in, need confirm true, and are snapshotted so they can be restored; WPForms has no delete. Forminator and SureForms keep entries in tables WP MCP cannot snapshot, so their delete-entry is off by default, needs confirm true, and is permanent.
Does a reversible delete count as a GDPR erasure?
No. A copy of the entry stays in the snapshot history until it is pruned, so a reversible delete is not an erasure.
All WP MCP guides, or see every plugin integration. Topic: Forms and data tables.