Get the plugin
WP MCP/Integrations/Forms

Forms integration

Formidable Forms AI agent tool reference

Formidable Forms keeps its forms and submissions in its own tables, reached through the FrmForm, FrmField, FrmFormAction and FrmEntry models. WP MCP Pro exposes them as a formidable-read and formidable-write pair: list forms, read a form and its fields, read its email notifications and confirmations (Formidable models them as email and on_submit form actions), list a form's entries and read a single entry. Once a site opts in with the wpmcp_enable_forms_write filter, the agent can edit an email action, change its to, cc and bcc recipients, edit a confirmation, and delete an entry. Recipient changes, confirmation edits and deletes need confirm:true. An action edit snapshots the action's post and rollback-operation restores it; a delete snapshots every frm_items and frm_item_metas row it removes, child entries included, and rollback-session puts them back. Entry operations and every write sit behind manage_options because submissions are personal data.

formidable-readformidable-writelist-notificationslist-entriesupdate-notificationdelete-entry

In practice

How Formidable Forms work goes with an agent.

Formidable Forms is built around its own model classes: FrmForm for forms, FrmField for fields, FrmFormAction for what happens on submit, and FrmEntry for submissions. Email notifications are not a separate setting. Formidable stores them as form actions of type email, which is why a question like "who gets this form" needs the action list rather than the form options. WP MCP Pro reads through those classes, so the same calls work whatever field types a form uses. Reads cover triage and reporting, and once the site opts in, the agent can also edit email actions and confirmations and delete entries, each snapshotted first.

List my Formidable forms with their keys, and show the fields on the Booking form.

Runs formidable-read with list-forms, then list-fields for that form_id. Fields come back with id, key, type, label, whether they are required and the options for choice fields. Read only.

Who gets emailed when the Feedback form is submitted, from what address, and with what subject?

Runs list-notifications, which reads the form's "email" form actions with their name, active state, recipient, sender, subject and message template. Read only, nothing is sent.

Summarise this week's Booking entries and flag any that mention a refund.

Runs list-entries with page_size and offset, newest first, then get-entry for the ones to read closely. Both need manage_options because entries are personal data. The agent does the summarising; nothing is written.

Change the Booking form's admin email subject to "New booking request".

Runs formidable-write with update-notification, which is off until the site enables wpmcp_enable_forms_write. The email action's post is snapshotted first, the response shows the subject before and after, and rollback-operation restores it.

What your AI can do

Real Formidable Forms operations, every write reversible.

  • List Formidable forms with names and keys
  • Read a form's fields, email notifications and confirmations
  • List a form's entries and read a single entry
  • Edit an email action and change its recipients (opt-in, reversible)
  • Edit a confirmation message, page or redirect (opt-in, confirm:true, reversible)
  • Delete an entry with its values and child entries (opt-in, confirm:true, restorable with rollback-session)

Example prompts

Example Formidable Forms prompts.

How many Booking form entries came in this week?

Who gets emailed when the Feedback form is submitted?

Read entry 512 and tell me what the customer asked for.

Under the hood

The Formidable Forms calls, under the hood.

wpmcp, formidable

formidable-read({ operation: "list-notifications", args: { form_id: 5 } }), email form actions

formidable-read({ operation: "list-entries", args: { form_id: 5 } }), paged

formidable-write({ operation: "update-notification", args: { form_id: 5, notification_id: 31, subject: "New booking request" } }), opt-in; snapshotted, rollback-operation

Safety and access

What can be undone on Formidable Forms, and what costs what.

Recoverable on Formidable Forms

  • update-notification, set-notification-recipients and update-confirmation snapshot the form action's post before it changes, and rollback-operation restores it.
  • delete-entry snapshots every frm_items and frm_item_metas row it removes, child entries from a repeater or embedded form included, and rollback-session puts them back.

Formidable Forms limits and opt-ins

  • Every write is off until the site opts in with the wpmcp_enable_forms_write filter.
  • set-notification-recipients, update-confirmation and delete-entry need confirm:true.
  • delete-entry removes rows directly, so Formidable's own delete hooks do not run and uploaded files stay on disk; an entry with a payment or subscription record is refused.
  • There is no entry status write, because Formidable entries are either draft or submitted and have no spam or trash state to move between.
  • Forms and fields are read only, and a confirmation still kept in the form options is listed as legacy and read only.
  • Entry operations and every write need manage_options on top of the pair's own capability.

Free or Pro: The Formidable integration is part of the Pro forms pack in the plugin source, and the formidable-read and formidable-write tools register only with a Pro licence and while Formidable is active. Formidable's own edition does not matter: the adapter uses its FrmForm and FrmEntry classes, which both editions load.

Part of WP MCP Pro

The Formidable Forms integration is part of WP MCP Pro.

One Pro licence unlocks the Formidable 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

Formidable Forms MCP: questions, answered.

Why is there no entry status write for Formidable?

Formidable has no spam or trash state for an entry: it is a draft or submitted. There is nothing for update-entry-status to move between, so the writes cover notifications, confirmations and entry deletion instead.

With Formidable Forms, can the agent delete entries?

Yes, once the site opts in with the wpmcp_enable_forms_write filter, and only with confirm:true. delete-entry removes the entry and, for a repeater or embedded form, its child entries, directly from frm_items and frm_item_metas, so Formidable's own delete hooks do not run and uploaded files stay on disk. It is refused for an entry with a payment or subscription record. Every row is snapshotted first and rollback-session puts them back.

Is the Formidable Forms integration part of the free plugin?

It is part of the Pro forms adapter pack. It uses Formidable's own models, so Formidable Pro fields and forms read the same way.

Why is there no status write?

An entry has no spam or trash state to move between, so update-entry-status would have nothing to do. The writes the integration does offer are email action and confirmation edits and an opt-in, confirmed entry delete that rollback-session can undo.

How does it find the email notifications?

Formidable models notifications as form actions of type email, so list-notifications calls FrmFormAction for the form's email actions. Each row shows its id, name, active state, recipient, sender, subject and message template. Other action types, such as webhooks or payments, are not listed there.

What does an entry read include?

get-entry returns the field values for one entry id with its metadata, and an entry listing is paged, newest first, with page_size up to 100 and an offset. The response includes the draft flag so an agent can tell a saved draft from a completed submission.

Does the Formidable Forms integration expose entry IP addresses?

Entry detail can include the submitter's IP where Formidable stores it, which is one reason entry operations are limited to manage_options. If you pass an entry to an agent, treat it as personal data under your privacy policy, as you would the entry screen.

Is there an AI agent for Formidable Forms?

Yes, through WP MCP rather than Formidable Forms itself. An agent you choose, such as Claude or Cursor, can list Formidable forms with names and keys. WP MCP is a separate plugin, not a built-in AI feature of Formidable Forms. On the undo side: update-notification, set-notification-recipients and update-confirmation snapshot the form action's post before it changes, and rollback-operation restores it.

Point your AI at Formidable Forms.