Get the plugin
WP MCP/Integrations/Forms

Forms integration

MCP for Forminator

Forminator keeps forms as its own post type and submissions in its own tables. WP MCP reads both through the public Forminator_API: list forms, read a form, list a form's entries and read one. A delete-entry op exists, but it is honest about its limits: Forminator's entry tables are not something WP MCP can snapshot, so the delete is off by default, needs confirm:true and manage_options, and answers recoverable:false. It is permanent.

forminator-readforminator-writelist-formslist-entriesdelete-entry

What your AI can do

Real Forminator operations, every write reversible.

  • List Forminator forms and read one
  • List a form's entries and read a single entry
  • Delete an entry (opt-in, confirm:true, not recoverable)

Example prompts

Just ask.

List my Forminator forms.

Summarize the last 20 entries on the Registration form.

Under the hood

The real calls.

wpmcp, forminator

forminator-read({ operation: "list-entries", args: { form_id: 12 } })

forminator-write({ operation: "delete-entry", args: { form_id: 12, entry_id: 90 }, confirm: true }), opt-in; recoverable:false

Frequently asked

Questions, answered.

Can a deleted Forminator entry be restored?

No. Forminator stores entries in tables WP MCP cannot snapshot, so the delete is permanent, off by default, and says recoverable:false. Use it only when you mean it.

Point your AI at Forminator.

Release notes, straight to your inbox.

One email per release, what shipped, what's verified, what's production-only. No drip campaigns. Unsubscribe in one click.