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-read and 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

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. Deletion is not offered on the Pro pack.

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. 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.