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.
IvyForms abilities, governed through the Bridge
An agent can list and read IvyForms forms, entries, notifications, integrations, templates and settings, create and duplicate forms, add and duplicate fields, update settings and notifications, star entries, publish or unpublish forms, and grant or revoke role and user permissions.
- Abilities
- 3919 read18 write2 destructive
- Active installs
- 1K+
- Rating
- 100% (9 ratings)
- Version checked
- 1.5.3
- Requires
- WP 5.0+, PHP 7.4+
- Last updated
- 2026-11-10
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View IvyForms on WordPress.org
What has to be true first
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.0), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
A note on the count below
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
The 39 IvyForms abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Read 19
- Read
Get Changelog
Retrieve the IvyForms changelog, including latest version updates, features, improvements, and bug fixes. Use this ability ONLY when the user explicitly asks for: - changelog - release notes - what changed in IvyForms - version updates or update history Do NOT use this ability for: - plugin settings - documentation - feature explanation unrelated to versions - support/debugging issues This is a READ-ONLY informational endpoint and does not modify any data.
- Read
List Entries
List IvyForms form entries (submissions) with pagination, optional text search, form filter, and sorting. Through this MCP ability, orderBy is limited to id or formName (matching the plugin list UI).
- Read
Get Entry
Retrieve a single IvyForms form entry (submission) by entryId. Returns the entry record plus field values suitable for inspecting one submission. Use this ability when the user asks to: - open or view details for one entry when its ID is known - inspect field values submitted in a single response DO NOT use this ability when the user wants: - multiple entries or a list/browse flow → use ivyforms/list-entries - form structure or builder fields → use ivyforms/get-form - notifications or emails → use notification abilities Entry content/status editing is not exposed as an MCP ability; only starring is available via ivyforms/update-entry-starred. This is READ-ONLY. The response includes adminLink when the entry resolves successfully.
- Read
Get Entry Count
Retrieve the total number of IvyForms entries (submissions) for one or more form IDs. This ability returns ONLY counts (aggregated numbers), not entry data. Use this ability when the user asks: - how many entries a form has - total submissions count - number of responses for one or more forms - entry statistics in the form of counts only DO NOT use this ability for: - listing actual entries → use ivyforms/list-entries - retrieving a single entry → use ivyforms/get-entry - searching or filtering entry data → use ivyforms/list-entries - analytics or reporting beyond simple totals This is a READ-ONLY aggregation endpoint and does not return individual entry records. Provide formIds as an array; the response includes counts keyed by each form ID.
- Read
List Forms
List all existing IvyForms forms. This ability is strictly for retrieving an overview of available forms and does NOT return full form details. WHEN TO USE: - Use when the user asks which forms exist, what forms they have, list/show/display forms, or how many forms exist. - Use for dashboards, overviews, or selection steps before operating on a specific form. WHAT IT RETURNS: - Form ID (if available) - Form name - Publication status (published/unpublished) - Admin link for navigation (use it to turn the name into a clickable markdown link) IMPORTANT RULES: 1. This is a READ-ONLY listing operation (no modifications happen). 2. Do NOT use this to fetch full form configuration; use get-form for that. 3. Do NOT use this to create or modify forms; use create-form or update-form-settings. 4. If a user refers to a specific form ID, prefer get-form instead. 5. This endpoint is safe for repeated calls and listing/overview workflows. AGENT BEHAVIOR GUIDELINES: - Always treat this as the entry point for form discovery. - Use adminLink for navigation instead of building URLs manually. - If user intent shifts to editing, transition to get-form → update-form-settings flow. COMMON MISTAKES TO AVOID: - Do NOT confuse this with get-form (single form details). - Do NOT assume field-level data is included. - Do NOT attempt updates or mutations from this ability.
- Read
Get Form
Get full details of a single IvyForms form using its formId. This ability returns complete form configuration including structure, fields, and settings. WHEN TO USE: - Use only when a specific formId is known or explicitly provided by the user. - Use when user requests to view, inspect, or edit a specific form. WHAT IT RETURNS: - Full form metadata (id, name, settings) - Complete field structure and layout - Configuration and behavior settings - Admin link for editing/navigation IMPORTANT RULES: 1. This is a READ-ONLY detailed fetch operation. 2. Do NOT use for listing or searching multiple forms; use get-forms instead. 3. This returns full structure and may be heavier than list operations. 4. Use this before any form editing or field modification workflows. AGENT BEHAVIOR GUIDELINES: - Always prefer this after form selection from get-forms. - Use adminLink for navigation or UI actions. - This is the canonical entry point for form editing context. COMMON MISTAKES TO AVOID: - Do NOT use for listing forms. - Do NOT assume this modifies data. - Do NOT skip this before edit operations.
- Read
List Integrations
Retrieve a list of all available IvyForms integrations. This ability is strictly for discovery and overview of integrations and does NOT return configuration details for a specific integration. WHEN TO USE: - Use when the user asks which integrations are available, what integrations exist, list/show integrations, or supported third-party services. - Use for marketplace views, onboarding, or integration selection flows. - Optionally use when filtering by plan tier (e.g. free/pro/enterprise). WHAT IT RETURNS: - Integration slug (identifier) - Integration name - Availability or plan tier (if applicable) - Basic metadata required for listing and selection IMPORTANT RULES: 1. This is a READ-ONLY discovery endpoint. No configuration data is modified. 2. Do NOT use this for fetching details of a specific integration; use get-integration instead. 3. Do NOT assume returned integrations are already configured for the user. 4. Do NOT use this for enabling, disabling, or modifying integrations. AGENT BEHAVIOR GUIDELINES: - Treat this as the starting point for integration selection workflows. - If user selects a specific integration, immediately switch to get-integration. - Use slug values as stable identifiers for follow-up calls. COMMON MISTAKES TO AVOID: - Do NOT confuse this with get-integration (single integration details). - Do NOT assume credentials or settings are included. - Do NOT attempt to configure integrations from this ability.
- Read
Get Integration
Retrieve detailed information about a specific IvyForms integration using its slug. This ability returns full integration metadata and configuration schema where applicable. WHEN TO USE: - Use ONLY when a specific integration slug is known (e.g. mailchimp, zapier, slack). - Use when the user asks for details, configuration, setup, or capabilities of a single integration. WHAT IT RETURNS: - Integration slug and name - Configuration requirements (API keys, tokens, etc.) - Supported features and capabilities - Setup instructions or metadata (if available) IMPORTANT RULES: 1. This is a READ-ONLY detailed lookup operation. 2. Do NOT use for listing all integrations; use list-integrations instead. 3. This does NOT enable or connect integrations automatically. 4. This only provides metadata and configuration structure. AGENT BEHAVIOR GUIDELINES: - Use this after selection from list-integrations. - Treat this as prerequisite before any integration setup workflow. - If user wants to connect an integration, this is the first step before configuration actions. COMMON MISTAKES TO AVOID: - Do NOT assume integration is active or connected. - Do NOT perform configuration changes from this ability. - Do NOT use for listing multiple integrations.
- Read
Open Form Builder
Returns the admin URL to open a specific form in the IvyForms builder. Use when the user asks to open, edit, or navigate to a form, its settings, or its results. Returns an adminLink the user can click to navigate to the form. Section values: "settings/general" for general settings, "settings/notification" (alias: "settings/notifications") for notifications, "settings/integrations" for integrations, "results/entries" for form entries/submissions.
- Read
Open Entry
Returns the admin URL to open a specific entry/submission details page. Use when the user asks to open, view, or go to a specific entry. Returns an adminLink the user can click to navigate to the entry.
- Read
List Notifications
Get all email notifications configured for a specific IvyForms form. This ability returns a complete list of notifications attached to a form, including their configuration and metadata. WHEN TO USE: - Use when the user asks to see all notifications for a form. - Use when the user wants an overview of email automations or messaging rules. - Use when checking what emails are sent after form submission. WHAT IT RETURNS: - Notification ID - Notification name - Sender / receiver configuration (if available) - Enabled/disabled status - Basic metadata for rendering or selection IMPORTANT RULES: 1. This is a READ-ONLY listing operation. No changes are made. 2. Do NOT use this to fetch full notification configuration for editing; use get-notification instead. 3. Do NOT create or modify notifications; use create-notification or update-notification. 4. Always treat results as a list view, not a detailed editor view. AGENT BEHAVIOR GUIDELINES: - Use this as the entry point for notification discovery. - If the user wants to edit a notification, first call this, then proceed to get-notification. - Use notificationId from results to navigate to deeper actions. COMMON MISTAKES TO AVOID: - Do NOT assume full email template content is included. - Do NOT modify notifications based on this response. - Do NOT confuse with search-notifications (which supports pagination and filtering).
- Read
Get Notification
Get detailed configuration of a single IvyForms email notification by its ID. This returns the full notification setup including email structure, rules, and settings. WHEN TO USE: - Use when user wants to view or inspect a specific notification. - Use when preparing to edit or duplicate a notification. - Use when debugging email delivery behavior. WHAT IT RETURNS: - Full notification configuration object - Sender, receiver, reply-to settings - Subject and message template - Enabled state and metadata IMPORTANT RULES: 1. This is a READ-ONLY operation. No changes are made. 2. Do NOT use this for listing multiple notifications; use list-notifications or search-notifications. 3. Always require a valid notificationId. AGENT BEHAVIOR GUIDELINES: - Use this before any update or duplication operation. - Treat response as source of truth for editing flows. COMMON MISTAKES TO AVOID: - Do NOT confuse with list-notifications. - Do NOT assume missing fields are optional in update context. - Do NOT modify data directly from this response.
- Read
Search Notifications
Search and paginate IvyForms email notifications with optional filters such as page, search term, and sorting. This is a flexible query-based listing tool for notifications. WHEN TO USE: - Use when user wants to find specific notifications by name or content. - Use when browsing large sets of notifications with pagination. - Use when filtering or sorting notification lists. WHAT IT RETURNS: - Filtered list of notifications - Pagination metadata (page, total, etc.) - Basic notification preview data IMPORTANT RULES: 1. This is a READ-ONLY search operation. 2. Do NOT use for fetching full notification configuration; use get-notification instead. 3. Results may be partial or paginated depending on parameters. AGENT BEHAVIOR GUIDELINES: - Use for discovery and filtering workflows. - Combine with get-notification for detailed inspection. COMMON MISTAKES TO AVOID: - Do NOT assume full notification payload is included. - Do NOT use for editing or deleting notifications. - Do NOT confuse with list-notifications (non-filtered overview).
- Read
Get Access Rules
List the current IvyForms permission (access) rules that grant roles and users access to forms, entries, and settings. READ-ONLY. Administrator access required. Use this before granting or revoking permissions so you know the current state.
- Read
List Permission Keys
List the available IvyForms permission keys (with labels) and the WordPress roles they can be assigned to. READ-ONLY. Administrator access required. Use this to discover valid permission keys before granting/revoking.
- Read
Get Settings
Get all IvyForms plugin settings in a single aggregated response. This ability provides a complete snapshot of the plugin configuration grouped by categories. WHEN TO USE: - Use when the user asks for settings overview, configuration summary, system settings, or plugin configuration state. - Use when the user wants to audit, inspect, or understand current IvyForms setup. - Use as a first step before updating or debugging settings. WHAT IT RETURNS: - Complete settings object grouped by categories - All available configuration keys and values IMPORTANT RULES: 1. This is a READ-ONLY operation (no changes are made). 2. Do NOT use this to update or modify settings; settings writes are not available via MCP. 3. Do NOT assume structure beyond returned payload. 4. Response may contain sensitive configuration values; handle carefully. AGENT BEHAVIOR GUIDELINES: - Use this as the entry point for debugging or configuration inspection. - Prefer this over multiple get-setting calls when global context is needed. - Do not attempt partial updates from this response. COMMON MISTAKES TO AVOID: - Do NOT treat this as a single-setting lookup (use get-setting for that). - Do NOT attempt to infer missing settings not returned in payload. - Do NOT modify values based on this response.
- Read
Get Setting
Retrieve a single IvyForms plugin setting by specifying its category and option key. This ability is designed for precise, targeted access to configuration values. WHEN TO USE: - Use when the user asks for a specific setting value (e.g. email config, API key, feature toggle). - Use when debugging a specific behavior tied to one configuration option. - Use when the user needs the current value before changing settings in the WordPress admin. WHAT IT RETURNS: - Single setting value for the requested category/option pair - Raw configuration value as stored in the system IMPORTANT RULES: 1. This is a READ-ONLY operation. 2. Requires BOTH category and option; partial queries are invalid. 3. Do NOT use for listing or browsing settings; use get-settings instead. 4. Output is minimal and scoped to a single configuration entry. AGENT BEHAVIOR GUIDELINES: - Always validate that category and option are explicitly known before calling. - If user intent is unclear or broad, fallback to get-settings instead. - Use before directing the user to change settings in the WordPress admin when needed. COMMON MISTAKES TO AVOID: - Do NOT use this to enumerate all settings. - Do NOT guess category/option names. - Do NOT treat partial matches as valid inputs.
- Read
List Templates
Get all available IvyForms form templates including metadata such as id, name, description, category, and pro availability flag. WHEN TO USE: - Use when the user asks what templates exist, available form starters, template library, or template options. - Use when creating a new form from a predefined structure (e.g. contact form, blank form, survey form). - Use when the user is browsing or comparing available form layouts before creation. WHAT IT RETURNS: - Template ID (unique identifier such as "blank_form", "contact_form") - Template name - Template description explaining purpose and use-case - Category grouping (e.g. business, contact, survey) - Pro flag indicating if template requires premium version IMPORTANT RULES: 1. This is a READ-ONLY discovery endpoint (no modifications). 2. Do NOT use this for creating forms; use create-form with templateId instead. 3. Do NOT assume template fields are included in this response; use get-template for full structure. 4. Results may be partial or grouped depending on system configuration. AGENT BEHAVIOR GUIDELINES: - Use this as the entry point for form creation workflows. - After selection, pass templateId directly to create-form. - Prefer this over guessing template IDs. COMMON MISTAKES TO AVOID: - Do NOT confuse templates with actual forms (use get-forms for forms). - Do NOT attempt to render full form structure from this endpoint. - Do NOT use this to modify templates.
- Read
Get Template
Retrieve complete IvyForms template definition by template ID, including all structure, fields, and configuration used to generate forms. WHEN TO USE: - Use when the user selects a specific template and wants to inspect its structure before creating a form. - Use when previewing or explaining what a template contains (fields, layout, configuration). - Use when debugging or validating template-based form creation. WHAT IT RETURNS: - Full template object including metadata (id, name, description) - Complete field structure and layout definition - Configuration required to generate a form from this template - Internal template schema used by the form builder IMPORTANT RULES: 1. This is a READ-ONLY detailed fetch operation. 2. Requires a valid templateId (e.g. blank_form, contact_form). 3. Do NOT use this for listing templates; use list-templates instead. 4. Response may be large because it includes full structure definition. AGENT BEHAVIOR GUIDELINES: - Use this only after a template is selected or explicitly requested. - Prefer list-templates for discovery and this for deep inspection. - Pass output directly into form creation workflows when needed. COMMON MISTAKES TO AVOID: - Do NOT call this without a known templateId. - Do NOT use this as a substitute for form data (it is not a live form). - Do NOT assume template equals editable form instance.
Write 18
- Write
Update Entry Starred
Mark an IvyForms entry as starred or unstarred (favorite toggle). This ability updates ONLY the "starred" status of an entry and does NOT modify entry content. Use this ability when the user wants to: - star an entry - mark an entry as important or favorite - unstar or remove star from an entry - toggle entry priority or bookmarking state DO NOT use this ability for: - editing entry field values or read/unread status (not exposed as an MCP ability) - listing or viewing entries → use list-entries or get-entry - bulk updates or modifications beyond star status This is a SAFE STATE CHANGE operation that only toggles a single boolean flag (starred/unstarred).
- Write
Add Form Field
Add a new field to an existing IvyForms form. Supported types: text, textarea, email, number, phone, website, name, radio, checkbox, select, multi-select, address, date, time, rating, html, slider, file-upload, gdpr, product, quantity, total. When IvyForms Pro is active, password, signature, date_time, likert, nps, and rich_text are also supported. After adding a field, use open-form-builder to let the user see and configure. For multipage forms (Pro), pass pageId (e.g. page_1) to place the field on a specific page.
- Write
Add Form Fields
Add one or more new fields to an existing IvyForms form. This ability modifies stored form configuration (writes the whole form payload like the builder save). REQUIRED INPUTS: formId and fields (each item requires type). Optional per-field keys mirror add-form-field. SUPPORTED FIELD TYPES: text, textarea, email, number, phone, website, name, radio, checkbox, select, multi-select, address, date, time, rating, html, slider, file-upload, gdpr, product, quantity, total. If IvyForms Pro is active, password, signature, date_time, likert, nps, and rich_text fields are also supported. IMPORTANT WORKFLOW RULES: 1. This ability ONLY adds fields to an existing form (it does NOT create a form). 2. If formId is missing or unknown, the agent MUST first use get-forms or create-form before calling this. 3. After successfully adding fields, the next step should usually be open-form-builder so the user can review layout and options. 4. Do not assume field ordering unless explicitly returned by the API response. FIELD BEHAVIOR NOTES: - label defaults to a capitalized version of type if not provided. - required defaults to false. - width defaults to 100 if not specified. - description is helper text shown under the field in UI. COMMON AGENT MISTAKES TO AVOID: - Do NOT call this if the user wants to create a form (use create-form instead). - Do NOT assume the field already exists after calling this ability until API confirms success. - Do NOT duplicate fields manually; use duplicate-form-field for that purpose.
- Write
Duplicate Form Field
Duplicate an existing field in an IvyForms form by its ID.
- Write
Reorder Form Fields
Reorder and adjust layout metadata for IvyForms form fields without changing field types or deleting them. Send formId plus a fields array listing each affected field id with its new position, and optionally rowIndex, columnIndex, width, and pageId (multipage / Pro). Unlike duplicate-form-field, this updates existing records in place via a form save. REQUIRED INPUTS: formId, and for each element in fields: id and position (per input schema). After reordering, use open-form-builder if the user should verify layout in the UI.
- Write
Create Form
Create a new IvyForms form from a template. This creates a fresh form instance but does NOT fully configure it. WHEN TO USE: - Use when user requests creation of a new form or starting a new form project. - Use when a template-based form is requested (e.g. blank_form, contact_form). WHAT IT RETURNS: - Newly created form ID - Admin link to access the form builder - Creation status message IMPORTANT RULES: 1. This is a DESTRUCTIVE WRITE operation (creates new persistent data). 2. Do NOT use for updating existing forms; use update-form-settings instead. 3. Do NOT use for adding fields; use add-form-field after creation. 4. Do NOT assume form is fully configured after creation. AGENT BEHAVIOR GUIDELINES: - After creation, immediately suggest next steps: settings → fields → publish. - Always guide user to update-form-settings for customization. COMMON MISTAKES TO AVOID: - Do NOT treat this as full form setup. - Do NOT add fields inside this operation. - Do NOT assume publishing happens automatically.
- Write
Duplicate Form
Duplicate an existing IvyForms form by formId, creating an independent copy. The new form contains the same structure, fields, and configuration as the original. WHEN TO USE: - Use when user wants to copy, clone, or reuse an existing form. - Use when user wants a template based on an existing form. WHAT IT RETURNS: - New form ID - Admin link for the duplicated form - Copy status message IMPORTANT RULES: 1. This is a DESTRUCTIVE WRITE operation (creates new form). 2. The original form is never modified. 3. Do NOT use for editing or updating forms. AGENT BEHAVIOR GUIDELINES: - Treat duplication as a starting point for a new workflow. - After duplication, suggest update-form-settings or add-form-field depending on intent. COMMON MISTAKES TO AVOID: - Do NOT modify original form. - Do NOT confuse with create-form (template-based creation).
- Write
Update Form Settings
Update general settings of an existing IvyForms form. This includes metadata and UI behavior, but NOT fields or entries. WHEN TO USE: - Use when user wants to rename a form, change description, publish/unpublish, or adjust visibility settings. - Use for configuration-level updates only. WHAT IT UPDATES: - Form name (max 255 characters) - Description (max 1000 characters) - Published status (draft/live) - UI settings (showTitle, showDescription, storeEntries) IMPORTANT RULES: 1. This is a WRITE operation affecting form metadata only. 2. Do NOT use for modifying fields (use field abilities instead). 3. Do NOT use for entries or submissions. 4. Do NOT use for structural changes. AGENT BEHAVIOR GUIDELINES: - Always ensure form exists via get-form before updating. - After update, confirm status and optionally suggest open-form-builder. COMMON MISTAKES TO AVOID: - Do NOT modify fields here. - Do NOT assume content structure changes. - Do NOT use for entry-level operations.
- Write
Update Form Starred
Toggle starred (favorite) status of an IvyForms form. This is purely a UI/organizational flag and does NOT affect form behavior. WHEN TO USE: - Use when user wants to mark a form as important or favorite. - Use when user wants to remove a form from favorites. WHAT IT AFFECTS: - Only the starred flag (true/false) - No structural or behavioral changes IMPORTANT RULES: 1. This is a SAFE metadata update. 2. Does NOT affect publishing or visibility. 3. Does NOT affect form data or structure. AGENT BEHAVIOR GUIDELINES: - Use for quick organization workflows. - Can be safely called multiple times. COMMON MISTAKES TO AVOID: - Do NOT treat as publishing action. - Do NOT confuse with status update.
- Write
Update Form Status
Publish or unpublish an IvyForms form. Controls whether a form is live (public) or in draft (hidden). WHEN TO USE: - Use when user wants to make a form live or disable public access. - Use when toggling availability of a form. WHAT IT AFFECTS: - Form visibility (published vs unpublished) - Public accessibility of the form IMPORTANT RULES: 1. This is a SAFE STATUS update operation. 2. Does NOT modify structure, fields, or entries. 3. Does NOT delete or alter data. AGENT BEHAVIOR GUIDELINES: - Always confirm intent before publishing/unpublishing. - Prefer this over delete when user says "disable" or "hide". COMMON MISTAKES TO AVOID: - Do NOT modify settings or fields here.
- Write
Setup Multipage Form
Configure multipage structure for an existing IvyForms form. Requires IvyForms Pro. Defines the ordered pages array (page_1, page_2, …), optional progress indicator settings, and optional per-field page assignments. Use after create-form and before or after add-form-field. Pair with reorder-form-fields (pageId) and add-form-field (pageId) to place fields on pages.
- Write
Add Form Page
Add a new page to an existing IvyForms multipage form. Requires IvyForms Pro. Appends a page by default, or inserts after insertAfterPageId. Page IDs are normalized on save (page_1, page_2, …). Use add-form-field with pageId or reorder-form-fields with pageId to populate the new page.
- Write
Create Notification
Create a new email notification for an IvyForms form. This defines automated email behavior triggered after form submission. WHEN TO USE: - Use when the user wants to add a new email automation rule. - Use when setting up confirmation emails, admin alerts, or user notifications. - Use after a form is created if email behavior is required. WHAT IT CREATES: - A new notification rule attached to a specific form - Email sender, receiver, subject, and message configuration - Enabled/disabled state for automation control IMPORTANT RULES: 1. This is a DESTRUCTIVE CREATE operation. A new notification is added. 2. Always ensure formId is valid before calling. 3. Default values may be applied if sender/receiver are omitted. 4. Do NOT use this for editing existing notifications; use update-notification instead. AGENT BEHAVIOR GUIDELINES: - After creation, always confirm success using returned notification data. - If user wants customization, follow up with update-notification or update-notification-settings. COMMON MISTAKES TO AVOID: - Do NOT duplicate notifications unintentionally. - Do NOT assume notification is active unless explicitly set. - Do NOT use this for bulk updates.
- Write
Update Notification
Update an existing IvyForms email notification by modifying one or more of its fields. Only provided fields are changed; all others remain untouched. WHEN TO USE: - Use when the user wants to edit email content, recipients, or behavior. - Use when adjusting notification rules after creation. - Use when fixing incorrect email settings. WHAT IT CAN UPDATE: - Name of the notification - Sender, receiver, reply-to emails - Subject and message content - Enabled/disabled state - Advanced display settings (e.g. showEmptyFields) IMPORTANT RULES: 1. This is a PARTIAL UPDATE operation (patch-style behavior). 2. Always fetch current state first using get-notification before updating. 3. Do NOT overwrite fields that are not explicitly provided. 4. Email fields must be sanitized before submission. AGENT BEHAVIOR GUIDELINES: - Always prefer minimal updates instead of full replacement. - If user request is ambiguous, retrieve current notification first. COMMON MISTAKES TO AVOID: - Do NOT reset fields unintentionally. - Do NOT assume missing fields should be cleared. - Do NOT bypass validation rules for email formatting.
- Write
Update Notification Settings
Update only the core settings of an IvyForms email notification. This is a simplified update focused on commonly edited fields from the UI. WHEN TO USE: - Use when user wants to quickly adjust notification behavior. - Use for toggling active/enabled state. - Use for simple edits like subject or receiver changes. WHAT IT AFFECTS: - Active/enabled state of notification - Name of notification - Receiver email address - Reply-to email address - Email subject line IMPORTANT RULES: 1. This is a SAFE-SCOPE UPDATE (limited fields only). 2. Prefer this over full update-notification when only basic settings change. 3. active and enabled are treated as aliases. 4. Always validate notificationId before applying changes. AGENT BEHAVIOR GUIDELINES: - Use this for quick toggles and simple edits. - Use full update-notification for message/template changes. COMMON MISTAKES TO AVOID: - Do NOT use this for message body editing. - Do NOT assume full notification structure is editable here. - Do NOT confuse active/enabled semantics; they are equivalent.
- Write
Duplicate Notification
Create a copy of an existing IvyForms email notification using its ID. The duplicated notification inherits all settings from the original. WHEN TO USE: - Use when user wants to reuse an existing email setup. - Use when creating variations of notifications (e.g. admin vs user emails). - Use when testing modifications safely without affecting original. WHAT IT DOES: - Copies sender, receiver, subject, message, and settings - Creates a new independent notification entry IMPORTANT RULES: 1. This is a CREATE operation based on an existing template. 2. The original notification is NOT modified. 3. The new notification is independent and can be edited separately. AGENT BEHAVIOR GUIDELINES: - Use duplication instead of rebuilding notifications manually. - After duplication, always suggest editing via update-notification. COMMON MISTAKES TO AVOID: - Do NOT assume links or IDs are shared between original and copy. - Do NOT overwrite original notification. - Do NOT treat as partial update.
- Write
Grant Role Permission
Grant one or more IvyForms permissions to a WordPress role. Administrator access required. Optionally limit the grant to specific form IDs (omit formIds to grant globally). Valid permission keys: view_forms_list, add_edit_forms, delete_forms, access_settings_page, view_entries_admin, delete_entries_admin. Use list-permission-keys to discover keys/roles and get-access-rules to review the result.
- Write
Grant User Permission
Grant one or more IvyForms permissions to a specific WordPress user. Administrator access required. Identify the user by userId, or by userLogin/userEmail. Optionally limit the grant to specific form IDs (omit formIds to grant globally). User-targeted grants override role-targeted grants for the same permission.
Destructive 2
- Destructive
Revoke Role Permission
Revoke one or more IvyForms permissions from a WordPress role. Administrator access required. Optionally limit the revoke to specific form IDs (omit formIds to revoke from global rules only). If a role rule has no permissions left afterwards it is removed entirely. Use get-access-rules to review the current grants first.
- Destructive
Revoke User Permission
Revoke one or more IvyForms permissions from a specific WordPress user. Administrator access required. Identify the user by userId, or by userLogin/userEmail. Optionally limit the revoke to specific form IDs (omit formIds to revoke from global rules only). If a user rule has no permissions left afterwards it is removed entirely.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install IvyForms and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. IvyForms registers its own abilities; this plugin discovers and governs them.
Open the Plugins’ own tools screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from IvyForms 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 IvyForms work with the Bridge?
Yes. IvyForms calls wp_register_ability() for 39 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Do IvyForms's abilities register automatically?
Yes, once IvyForms is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
Does IvyForms need anything special to work with the Bridge?
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.0), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
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.
An 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.
Verified from IvyForms's own free wordpress.org code (version 1.5.3) on 10 November 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, Melograno Venture Studio or IvyForms. Back to the full directory.
Bridge IvyForms, 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.