Forms integration
MetForm MCP
MetForm is an Elementor-based form builder: forms are a post type with their layout in _elementor_data, and every submission is its own post with a field map in post meta. Because those are ordinary WordPress objects, WP MCP reads them with core APIs, and its delete-entry is genuinely reversible: the entry row and its meta are snapshotted before the delete, and rollback-operation brings the submission back at its original id with its values intact. The delete still needs confirm:true and manage_options, since a submission is personal data.
In practice
How MetForm work goes with an agent.
MetForm is built on Elementor, and both halves of its data are ordinary WordPress objects. A form is a metform-form post with its layout in the Elementor data, and every submission is its own metform-entry post with a field-name-to-value map in meta. WP MCP reads them with core post functions and no MetForm internals. That is why MetForm is the one forms adapter where deleting a submission can be undone: the entry is a post, so its row and meta can be snapshotted first.
List my MetForm forms and how many submissions each has received.
Runs metform-read with list-forms. It returns id, title, status, entry count and the [metform form_id="N"] shortcode, for forms the caller may read. Read only.
Which fields does the quote request form collect, and which are mandatory?
Runs get-form, which walks the Elementor layout for MetForm input widgets and returns each field's name, label, type and required flag.
Show the ten newest submissions on form 7 and flag any with an empty phone number.
Runs list-entries with form_id 7 and page_size 10. Entries come newest first with their stored values. Entry reads need manage_options, since submissions are personal data.
Delete entry 905, it is a test.
Runs delete-entry, which is off by default and needs confirm:true and manage_options. The entry row and its meta are snapshotted first, and the response carries an operation_id and recoverable:true.
What your AI can do
Real MetForm operations, every write reversible.
- List MetForm forms and read one
- List a form's submissions and read one with its field values
- Delete a submission, snapshotted and restorable at its original id
Example prompts
Example MetForm prompts.
List my MetForm forms and their submission counts.
Read the latest submission on the Booking form.
Delete the three test submissions from this morning.
Under the hood
The MetForm calls, under the hood.
metform-read({ operation: "list-entries", args: { form_id: 18 } })
metform-write({ operation: "delete-entry", args: { entry_id: 402 }, confirm: true }), snapshotted; recoverable:true
Safety and access
What can be undone on MetForm, and what costs what.
Recoverable on MetForm
- delete-entry snapshots the entry post and all its meta before it deletes.
- rollback-operation with the returned operation_id restores the submission at its original id with its values intact.
- The form and entry reads write nothing.
MetForm limits and opt-ins
- delete-entry is off until a site opts in with the wpmcp_integration_op_enabled filter, and it needs confirm:true.
- delete-entry needs manage_options on top of the pair's own capability. So do entry reads.
- The operations are list-forms, get-form, list-entries, get-entry and delete-entry. There is no operation to edit a form's layout or settings.
Free or Pro: The MetForm integration is free, and it registers only while MetForm is active, as a metform-read and metform-write pair. Reads of forms and fields use the pair's normal capability, and entry reads need manage_options. The one write, delete-entry, is opt-in, and unlike SureForms it is reversible. Pro adds no MetForm operations.
In the free plugin
The MetForm integration is in the free plugin.
The core MetForm tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
MetForm MCP: questions, answered.
Is a MetForm delete a GDPR erasure?
No. Because it is reversible, a copy of the submission stays in the snapshot history until it is pruned.
Why can MetForm entries be restored but SureForms entries cannot?
A MetForm entry is a normal post with post meta, and WP MCP's snapshot engine already captures and restores posts at their original id. SureForms keeps submissions in a custom database table that the engine cannot snapshot, so its delete is permanent and flagged recoverable:false.
How does it read the form's fields?
It decodes the form's Elementor data and collects every widget that carries a MetForm input name. The field name, label and required flag come from the widget settings, and the type comes from the input type or the widget name without its mf prefix. Nested sections and columns are walked.
Do I need Elementor active for this?
MetForm itself needs Elementor to build forms, so any site with forms has it. The integration switches on when MetForm is loaded, and reading field definitions depends on the Elementor data stored on each form, which is how MetForm saves its layouts.
Related integrations
More integrations for the same agent.
MCP for Elementor Pro Forms
ProForms, 2 tools.
MCP for WPForms
ProForms, 5 tools.
MCP for Contact Form 7
FreeForms, 5 tools.
MCP for SureForms
FreeForms, 5 tools.
MCP for Forminator
FreeForms, 5 tools.
MCP for Gravity Forms
ProForms, 6 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.