Forms integration
WS Form MCP
WS Form keeps everything in tables of its own. WP MCP reads them directly: wsform-list-forms, wsform-get-form, wsform-list-fields, wsform-list-actions, wsform-list-notifications (the email actions), wsform-list-entries and wsform-get-entry. Submission counts are counted from the submissions table, not taken from WS Form's cached columns, and a listing masks every field value and leaves out tracking data such as the IP address, while reading one entry returns it in full; entries saved with WS Form's encryption on are decrypted the way WS Form reads them. Writes are off until a site opts in: wsform-update-entry-status sets status, starred and viewed on the submission row directly rather than through the status hook that could report the sender's IP to an external service, under a before-image of that row; wsform-delete-entry permanently deletes a submission with its values and notes, asking for confirm:true and capturing the rows so rollback-session reinserts them. Every op takes manage_options, since WS Form grants its capabilities to administrators and submissions are personal data.
In practice
How WS Form work goes with an agent.
WS Form, in both the Lite and Pro editions, keeps every form in tables of its own: forms, tabs, sections and fields as last saved in the editor, actions stored as a serialized grid in form meta, and submissions as rows in wsf_submit with their values in a meta table. WP MCP is built around the privacy of those submissions. Listings mask every value and leave out tracking data such as the IP address, a single entry is read in full on request, and entries saved with WS Form encryption on are decrypted the way WS Form decrypts them.
List my WS Form forms with the real submission counts.
Runs wsform-list-forms. Counts come from the wsf_submit table instead of WS Form's cached columns, which only refresh when WS Form itself writes. Read only, and available on the free plugin.
What does the job application form email, and who receives it?
Runs wsform-list-actions to see the form's actions, then wsform-list-notifications for just the email actions. Both read the form's saved action grid. Read only.
Show me entry 44 in full, it came in encrypted.
Runs wsform-get-entry, which returns every field value, the tracking data and the notes, and decrypts values for a submission saved with encryption. Listings stay masked. It needs manage_options, and is read only.
Star entry 44, mark it viewed, and send entries 50 to 53 to spam.
Runs wsform-update-entry-status, which is off until the site enables wpmcp_enable_ws_form_write. It writes the wsf_submit row directly instead of through WS Form's status hook, under a before-image of that row, so rollback-operation can undo each.
What your AI can do
Real WS Form operations, every write reversible.
- List forms, fields, actions and email notifications
- List entries with values masked and tracking data left out
- Read one entry in full, decrypting encrypted submissions
- Set an entry's status, starred and viewed (opt-in), reversible
- Permanently delete an entry with confirm:true, reinsertable from the session
Example prompts
Example WS Form prompts.
List the WS Form forms and how many entries each has.
Show me the fields on the job application form.
Mark the obvious spam entries on the contact form as spam.
Under the hood
The WS Form calls, under the hood.
plugin-data-read({ integration: "ws-form", operation: "wsform-list-entries", args: { form_id: 3 } }), values masked, no tracking data
plugin-data-write({ integration: "ws-form", operation: "wsform-update-entry-status", args: { entry_id: 44, status: "spam" } }), opt-in; row before-image, reversible
Safety and access
What can be undone on WS Form, and what costs what.
Recoverable on WS Form
- wsform-update-entry-status takes a before-image of the one wsf_submit row, so rollback-operation restores status, starred and viewed.
- wsform-delete-entry captures the submission rows, its values and its notes in one session, and rollback-session reinserts them with their original ids.
- Setting a spam status also sets WS Form's spam level (100), and restoring publish clears it, as WS Form does.
WS Form limits and opt-ins
- Both writes are off until a site opts in with the wpmcp_enable_ws_form_write filter.
- wsform-delete-entry permanently removes a submission and needs confirm:true. A trash status is the gentler option.
- Uploaded files stay on disk when an entry is deleted, so a restored submission still links to them.
- Listings mask field values and omit tracking data. Only wsform-get-entry returns an entry in full.
- Every operation needs manage_options, since submissions are personal data.
Free or Pro: WS Form is a free-tier integration, and the free plugin gives you the reads on both WS Form editions. The writes are not gated by licence but by an opt-in: wsform-update-entry-status and wsform-delete-entry stay off until the site sets wpmcp_enable_ws_form_write. The operations ride on the plugin-data pair as wsform-* names, so they add no top-level tools. Form, field and action definitions are read only.
In the free plugin
The WS Form integration is in the free plugin.
The core WS Form 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
WS Form MCP: questions, answered.
Is the WS Form integration free?
Yes. It works with both WS Form editions and is a free-tier integration. The entry writes stay off until a site opts in with the wpmcp_enable_ws_form_write filter.
Why does setting a status write the row directly?
WS Form's own status hook can report the sender's IP to an external abuse service, which no undo could withdraw, so WP MCP writes the row itself and snapshots it, keeping the change reversible.
Why are entry values masked in listings?
A listing is the most likely thing to be pasted into a chat or logged, so wsform-list-entries masks every field value in an a@*** style and leaves out the IP address and other tracking data. When the agent needs the real content it reads one entry with wsform-get-entry, which is deliberate and manage_options only.
What is the difference between trash and delete?
Setting the status to trash through wsform-update-entry-status keeps the submission inside WS Form, where it can be restored. wsform-delete-entry removes the submission, its values and its notes from the tables, needs confirm:true, and relies on rollback-session to reinsert them. Uploaded files are not removed either way.
Does it work on WS Form Lite?
Yes. The integration keys on WS Form being loaded and on its tables existing, and both editions define the same version constant. Forms, fields, actions, notifications and submissions are read from the tables directly, so the reads behave the same on Lite and Pro.
Does marking an entry as spam report the sender anywhere?
No. WS Form's own status function can send the sender's IP to an external abuse-reporting service. WP MCP writes the row itself instead, so no report goes out and the change stays a local, reversible edit. The row is snapshotted before the write.
Related integrations
More integrations for the same agent.
MCP for Gravity Forms
ProForms, 6 tools.
MCP for Formidable Forms
ProForms, 6 tools.
MCP for Contact Form 7
FreeForms, 5 tools.
MCP for WPForms
ProForms, 5 tools.
MCP for Ninja Forms
ProForms, 5 tools.
MCP for Fluent Forms
ProForms, 6 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.