Forms integration
Fluent Forms AI agent tool reference
Fluent Forms stores forms, notifications and submissions in its own tables, reached through the wpFluent() query builder. WP MCP Pro exposes them as a fluentforms-read and fluentforms-write pair: list forms, read fields and email notifications, list submissions (trashed ones left out by default, as Fluent Forms' own screen does) and read one. update-entry-status sets a submission to unread, read, spam or trashed and fires the same action Fluent Forms fires, so add-ons listening for status changes still hear about it. The write is snapshotted as a before-image of exactly that row, and rollback-operation restores it. Once a site opts in with the wpmcp_enable_forms_write filter, delete-entry (confirm:true) removes a submission with its meta, logs and entry details, snapshotting every row first so rollback-session puts them back; it is refused for a submission with a payment record. Notifications are read only.
Fluent Forms in plain language: Fluent Forms MCP.
In practice
How Fluent Forms work goes with an agent.
Fluent Forms keeps forms and their fields in one table, email notifications as meta rows named notifications, and submissions in another table with a status column. That column has four values (unread, read, spam and trashed), and Fluent Forms fires its own action whenever one changes, so add-ons such as notification and integration plugins react. WP MCP reads all of it through the wpFluent() query builder and writes the status, firing that same action, and once the site opts in it can also delete a submission. Because these are rows in plugin tables, the undo is a row before-image, not a post snapshot.
What does the Signup form collect, and what does its admin notification say?
Runs get-form for the decoded fields, list-fields for each input name, element type, label and required flag, and list-notifications for the id, name, enabled flag, recipient, subject and message template. All reads.
List the unread submissions on form 4 and read the newest.
Runs list-entries with form_id 4 and status unread, newest first, then get-entry, which returns the submitted response, serial number, date and IP address. Both need manage_options.
Which of last week's submissions look like spam? Mark them.
Reads with list-entries and get-entry, then runs update-entry-status with status spam on each one the agent flags. Each call takes a before-image of that row and fires Fluent Forms' after-status-update action.
Show me the trashed submissions on form 4.
Runs list-entries with status trashed. Without a status, trashed entries are left out, as on Fluent Forms' own entries screen, so they only appear when asked for.
What your AI can do
Real Fluent Forms operations, every write reversible.
- List Fluent Forms forms and read their decoded fields
- Read a form's email notifications
- List and read submissions
- Set a submission to unread, read, spam or trashed, reversibly
- Delete a submission (opt-in, confirm:true, restorable with rollback-session)
Example prompts
Example Fluent Forms prompts.
List my Fluent Forms and the fields each one collects.
Mark every submission on the Signup form from last week as read.
Which submissions look like spam? Mark them.
Under the hood
The Fluent Forms calls, under the hood.
fluentforms-read({ operation: "list-entries", args: { form_id: 4 } })
fluentforms-write({ operation: "update-entry-status", args: { entry_id: 77, status: "spam" } }), row snapshotted; Fluent Forms hook fires
Safety and access
What can be undone on Fluent Forms, and what costs what.
Recoverable on Fluent Forms
- update-entry-status writes a before-image of exactly that submission row before changing it.
- rollback-operation restores the previous status, and warns if the row has changed again in between.
- Setting the status back by hand, for example from spam to read, is also a normal write and is snapshotted too.
- delete-entry snapshots every row it removes from the submission, meta, logs and entry details tables in one session, and rollback-session puts them back.
Fluent Forms limits and opt-ins
- delete-entry is off until the site opts in with the wpmcp_enable_forms_write filter, needs confirm:true, and is refused for a submission with a payment, order or subscription record. Fluent Forms' own delete hooks do not run and uploaded files stay on disk.
- Forms, fields and notifications are read only: no op creates a form or edits a notification.
- Every entry op needs manage_options on top of the pair's own capability, since submissions carry personal data and an IP address.
- The write fires fluentform/after_submission_status_update, so listening add-ons run their own side effects, which an undo does not reverse.
Free or Pro: Fluent Forms support is Pro, in the forms adapter pack, and registers only while Fluent Forms is active. It needs only the free Fluent Forms plugin, through its wpFluent() query builder, not Fluent Forms Pro. The status write has no opt-in filter of its own, but it needs manage_options and a licensed WP MCP site. Deleting a submission also needs the site's opt-in and confirm:true. No op edits a form or a notification.
Part of WP MCP Pro
The Fluent Forms integration is part of WP MCP Pro.
One Pro licence unlocks the Fluent Forms tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
Fluent Forms MCP: questions, answered.
With Fluent Forms, can the agent delete submissions?
Yes, once the site opts in with the wpmcp_enable_forms_write filter, and only with confirm:true. The rows are removed directly, so Fluent Forms' own delete hooks do not run and uploaded files stay on disk, and a submission with a payment, order or subscription record is refused. Every row is snapshotted first and rollback-session restores them. Setting the status to trashed is the gentler option.
Is the Fluent Forms integration part of the free plugin?
It is part of the Pro forms adapter pack, and uses the standard wpFluent() query builder in the free Fluent Forms plugin.
Which submission statuses can be set?
unread, read, spam and trashed, the values Fluent Forms uses for an entry. update-entry-status writes the status column and then fires Fluent Forms' own after-status-update action, so the change behaves like one made in its admin. A trashed entry stays in the table and can be moved back; only the separate, opt-in delete-entry removes it.
Does marking a submission as spam notify other add-ons?
Yes. The write fires fluentform/after_submission_status_update, the action Fluent Forms' own service fires, so an add-on listening for status changes hears about it. That is also why an undo restores the row but cannot reverse what a listening add-on did in response, such as an outside request.
Where do the notifications come from?
From the form's meta rows named notifications, the same place Fluent Forms reads its email notifications from. list-notifications returns each one's id, name, whether it is enabled, who it is sent to, the subject and the message template, so an agent can check where a form's emails go without editing them.
What does reading one entry include?
get-entry returns the form, serial number, status, date, the submitted response and the IP address. That is personal data, so it needs manage_options, the same level as the listing. A listing returns the lighter rows, 20 per page by default and up to 100, with an offset to continue.
Is there an AI agent for Fluent Forms?
Yes, through WP MCP rather than Fluent Forms itself. An agent you choose, such as Claude or Cursor, can list Fluent Forms forms and read their decoded fields. WP MCP is a separate plugin, not a built-in AI feature of Fluent Forms. On the undo side: update-entry-status writes a before-image of exactly that submission row before changing it.
Related integrations
More integrations for the same agent.
MCP for WPForms
ProForms, 5 tools.
MCP for Gravity Forms
ProForms, 6 tools.
MCP for Formidable Forms
ProForms, 6 tools.
MCP for SureForms
FreeForms, 5 tools.
MCP for MetForm
FreeForms, 5 tools.
MCP for WS Form
FreeForms, 2 tools.
Browse the full Integrations hub, or read more on Fluent Forms MCP and the WordPress MCP plugin.