An agent can list and inspect WPForms forms and their fields, read (limited, Lite-only) form stats, and create new forms or add and update fields on existing ones.
4 read4 write
View abilitiesWS Form abilities, governed through the Bridge
An agent can list, read, and create forms, submissions, submission notes, and form styles, and, once the site enables the relevant option, edit or delete forms, fields, tabs, sections, and styles.
- Abilities
- 3513 read16 write6 destructive
- Active installs
- 10K+
- Rating
- 100% (322 ratings)
- Version
- 1.12.10
- Requires
- WP 5.5+, PHP 7.2+
- Last updated
- 2026-09-09 1:06am GMT
What has to be true first
WS Form and WordPress 6.9 or later must both be active for these abilities to appear in the registry. Reads require WS Form's own read_form, read_submission, or read_form_style capability; most write and delete abilities require the matching edit/create/delete capability plus a site option that is off by default, so a freshly installed site exposes only the read abilities and the few writes that are not option gated (form-create-json, form-publish, form-draft, form-clone, the submission note abilities, and style-create).
- The 5 style abilities (styles, style-get, style-create, style-update, style-delete) only register when the site's form style Framework setting is ws-form, the default, and the styler is not disabled by the wsf_styler_enabled filter
- Most write and delete abilities also require a dedicated option to be turned on (abilities_api_edit_form, abilities_api_delete_form, or abilities_api_delete_style, all off by default) in addition to the matching capability; they still register, but the permission check refuses the call until the option is enabled
- A wsf_config_abilities filter can add, remove, or change any ability before registration
The 35 WS Form abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 13
- Read
List forms
Lists all forms in WS Form, optionally filtered to published only.
- Read
Get form JSON
Returns a form's full JSON definition by ID.
- Read
Get form shortcode
Returns the shortcode used to embed a form.
- Read
Get form block markup
Returns the Gutenberg block markup used to embed a form.
- Read
Get form stats
Returns submission statistics for a form.
- Read
List submissions
Lists submissions for a form.
- Read
Get submission
Returns a single submission's field values.
- Read
List submission notes
Lists the notes attached to a submission.
- Read
List styles
Lists the form styles available on the site.
- Read
Get style
Returns a single form style's palette and settings.
- Read
List tabs
Lists a form's tabs (multi-step pages).
- Read
List sections
Lists a form's sections.
- Read
List fields
Lists a form's fields.
Write 16
- Write
Create form from JSON
Creates a new form from a JSON definition.
- Write
Update form from JSON
Replaces an existing form's structure and settings using a JSON definition.
- Write
Publish form
Publishes a draft form so it can be used on a live page.
- Write
Draft form
Sets a published form back to draft.
- Write
Clone form
Duplicates a form as a new draft.
- Write
Create submission note
Adds a note to a submission.
- Write
Update submission note
Edits an existing submission note.
- Write
Restore form
Restores a trashed form.
- Write
Add field
Inserts a new field into a form section.
- Write
Update field
Edits an existing field's label or settings.
- Write
Create style
Creates a new form style, optionally set as the site default.
- Write
Update style
Edits an existing form style's label or palette values.
- Write
Add tab
Adds a new tab (page) to a multi-step form.
- Write
Update tab
Edits an existing tab's label or settings.
- Write
Add section
Adds a new section to a form.
- Write
Update section
Edits an existing section's label or meta.
Destructive 6
- Destructive
Delete submission note
Permanently deletes a submission note.
- Destructive
Delete form
Trashes or permanently deletes a form.
- Destructive
Delete field
Removes a field from a form.
- Destructive
Delete style
Trashes or permanently deletes a form style.
- Destructive
Delete tab
Removes a tab from a form.
- Destructive
Delete section
Removes a section from a form.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install WS Form and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. WS Form registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from WS Form starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does WS Form work with the Bridge?
Yes. It registers 35 abilities under the wsf/ namespace with per-ability annotations and capability-based permission callbacks, so the Bridge can list and switch on each one.
What has to be true for WS Form's abilities to register?
The 5 style abilities (styles, style-get, style-create, style-update, style-delete) only register when the site's form style Framework setting is ws-form, the default, and the styler is not disabled by the wsf_styler_enabled filter. Most write and delete abilities also require a dedicated option to be turned on (abilities_api_edit_form, abilities_api_delete_form, or abilities_api_delete_style, all off by default) in addition to the matching capability; they still register, but the permission check refuses the call until the option is enabled. A wsf_config_abilities filter can add, remove, or change any ability before registration.
Does WS Form need anything special to work with the Bridge?
WS Form and WordPress 6.9 or later must both be active for these abilities to appear in the registry. Reads require WS Form's own read_form, read_submission, or read_form_style capability; most write and delete abilities require the matching edit/create/delete capability plus a site option that is off by default, so a freshly installed site exposes only the read abilities and the few writes that are not option gated (form-create-json, form-publish, form-draft, form-clone, the submission note abilities, and style-create).
More Forms plugins
Fluent Forms
ConditionalOnce MCP is turned on, an agent can read form schemas, entries, stats, integrations, notifications and styling, create and restyle forms, edit form fields, manage email notifications, and triage or bulk-update submissions including deletion.
12 read8 destructive
View abilitiesAn agent can build a complete form field by field, wire up actions and calculations, embed the form in a page, and read, export, update, or delete its submissions.
27 write5 destructive
View abilitiesVerified from WS Form's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Mark Westguard or WS Form. Back to the full directory.
Bridge WS Form, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.