Forms integration
SureForms MCP
SureForms is a block-based form builder: forms are a post type whose fields are srfm/* blocks, and submissions live in its own entries table. WP MCP reads field definitions by parsing the form's blocks, and reads entries only through SureForms' own entries accessor, so it survives schema changes. A delete-entry op exists but, because the entries table cannot be snapshotted, it is off by default, needs confirm:true and manage_options, and answers recoverable:false.
In practice
How SureForms work goes with an agent.
SureForms forms are a post type whose fields are srfm blocks inside the post content, so a form's definition is a block tree that can nest fields inside layout blocks. Its submissions are not posts at all. They live in SureForms' own entries table, and WP MCP reads them only through the plugin's own entries class, not raw SQL, so a schema change in SureForms does not break it. The result is a read view of forms and submissions, with one deliberately guarded delete.
List my SureForms forms with their entry counts and the shortcode for each.
Runs sureforms-read with list-forms. It returns id, title, status, entry_count and the [sureforms id="N"] shortcode, only for forms the caller may read. Read only.
What does the contact form ask for, and which fields are required?
Runs get-form, which walks the block tree, including blocks nested in layouts, and returns each field's name, label, type and required flag.
Show this week's submissions on form 30, grouped by the topic dropdown.
Runs list-entries with form_id 30, paged with page_size up to 100 and an offset. Each entry has its status, timestamp and decoded values. Entry reads need manage_options because submissions are personal data.
Delete entry 411, it is a test submission.
Runs delete-entry. It is off by default, needs confirm:true and manage_options, and answers recoverable:false because the entries table cannot be snapshotted. The agent should say so before it asks to run it.
What your AI can do
Real SureForms operations, every write reversible.
- List SureForms forms and read their block fields
- List a form's entries and read a single entry
- Delete an entry (opt-in, confirm:true, not recoverable)
Example prompts
Example SureForms prompts.
What fields does the SureForms contact form collect?
Show me this week's SureForms submissions grouped by topic.
Under the hood
The SureForms calls, under the hood.
sureforms-read({ operation: "get-form", args: { form_id: 30 } }), fields parsed from srfm blocks
sureforms-read({ operation: "list-entries", args: { form_id: 30 } })
Safety and access
What can be undone on SureForms, and what costs what.
Recoverable on SureForms
- The form and entry reads write nothing, so there is nothing to undo.
- There is no undo for delete-entry. SureForms entries cannot be snapshotted, so rollback-operation cannot bring one back.
SureForms 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 permanently removes the entry through SureForms' own entries class, and the response is flagged recoverable:false.
- Entry reads and the delete need manage_options, on top of the pair's own capability.
- The operations are list-forms, get-form, list-entries, get-entry and delete-entry. There is no operation to edit a form or change an entry's status.
Free or Pro: The SureForms integration is free. It registers only while SureForms is active, as a sureforms-read and sureforms-write pair. Reading forms and fields needs the pair's normal capability. Reading entries needs manage_options. The single write, delete-entry, is off by default and cannot be undone, which is why it is opt-in. Pro adds no SureForms operations.
In the free plugin
The SureForms integration is in the free plugin.
The core SureForms 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
SureForms MCP: questions, answered.
Is deleting a SureForms entry undoable?
No. The entries table is not a WP MCP snapshot target, so the delete is permanent, off by default, and flagged recoverable:false.
Why does it read entries through SureForms' own class?
Because the entries table is the plugin's private storage, and its columns can change between releases. Going through SureForms' entries accessor means WP MCP keeps working across those changes. It is also the same path SureForms uses to delete, so a delete behaves as it does in the plugin.
Will the SureForms integration see fields nested inside sections or columns?
Yes. SureForms nests field blocks inside layout blocks, and get-form walks the whole block tree. Each field comes back with its slug as the name, its label, its type (the block name without the srfm prefix) and whether it is required.
How many entries can one call return?
list-entries defaults to 20 and allows up to 100 per call, with an offset for the next page, and it also reports the total for the form. For a large form, the agent pages through, or asks you to narrow the question before it pulls hundreds of submissions.
Related integrations
More integrations for the same agent.
MCP for WPForms
ProForms, 5 tools.
MCP for Contact Form 7
FreeForms, 5 tools.
MCP for Forminator
FreeForms, 5 tools.
MCP for MetForm
FreeForms, 5 tools.
MCP for Fluent Forms
ProForms, 6 tools.
MCP for WS Form
FreeForms, 2 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.