Forms integration
Gravity Forms AI agent tool reference
Gravity Forms stores forms and their submissions in its own tables, reached through the public GFAPI. WP MCP Pro exposes that API as a gravityforms-read and gravityforms-write pair: list forms with their entry counts, read a form, its fields, notifications and confirmations, page through entries with a status filter, and read a single entry with its notes. update-entry-status moves an entry between active, spam and trash the way Gravity Forms' own entry screen does, snapshotted first as a before-image of exactly that row, so rollback-operation puts it back. Once a site opts in with the wpmcp_enable_forms_write filter, the agent can also edit a notification, change its to and bcc recipients, edit a confirmation, and delete an entry. Recipient changes, confirmation edits and deletes need confirm:true. Notification and confirmation edits are snapshotted as the form's gf_form_meta row and undone with rollback-operation; a delete snapshots every gf_entry, gf_entry_meta and gf_entry_notes row it removes, and rollback-session puts them back. Entry operations and every write sit behind manage_options because submissions are personal data.
Gravity Forms in plain language: Gravity Forms MCP.
In practice
How Gravity Forms work goes with an agent.
Gravity Forms keeps forms as serialized objects and submissions in its own gf_entry tables, and the supported way in is the GFAPI class. WP MCP Pro calls that API for every operation, so what the agent sees matches the Gravity Forms entry screen. A site with a Contact form, a Quote Request form and a Job Application form typically wants three things from an agent: what a form is wired to notify, what has come in lately, and which entries are spam. This integration covers those, and keeps the writes that go further (notification and confirmation edits, entry deletes) off until the site opts in.
Which Gravity Forms are inactive, and how many entries does each active form hold?
Runs gravityforms-read with list-forms. The default lists active forms, and active:false lists the inactive ones. Each row has the id, title, entry count and field count. Read only.
For the Quote Request form, list who gets notified, when, and what the subject line is.
Runs list-notifications for that form_id, which returns each notification's name, triggering event, active state, recipient, subject and message template. Read only, and it does not call any notification.
Pull the 20 newest spam-looking entries on form 1 and show me the notes on any with a reply.
Runs list-entries with page_size and offset, then get-entry and get-notes for the ones worth reading. All three need manage_options because submissions are personal data. Read only.
Move entries 512 and 514 to spam, they are obvious junk.
Runs gravityforms-write with update-entry-status once per entry. It calls GFAPI::update_entry_property, as the Gravity Forms entry screen does, after taking a before-image of that one gf_entry row, so rollback-operation puts the status back.
What your AI can do
Real Gravity Forms operations, every write reversible.
- List forms with entry counts and field counts
- Read a form's fields, notifications and confirmations
- Page through entries, newest first, filtered by status
- Read a single entry with all its field values and notes
- Move an entry between active, spam and trash, snapshotted and reversible
- Edit a notification and change its recipients (opt-in, reversible)
- Edit a confirmation message, page or redirect (opt-in, confirm:true, reversible)
- Delete an entry with its values and notes (opt-in, confirm:true, restorable with rollback-session)
Example prompts
Example Gravity Forms prompts.
How many entries did the Contact form get this month, and what are the common themes?
Show me who the Quote Request form notifies, and when.
Mark the obvious spam entries on the Contact form as spam.
Under the hood
The Gravity Forms calls, under the hood.
gravityforms-read({ operation: "list-entries", args: { form_id: 1, status: "active" } }), paged
gravityforms-write({ operation: "update-entry-status", args: { entry_id: 512, status: "spam" } }), row snapshotted, reversible
gravityforms-write({ operation: "delete-entry", args: { entry_id: 514 }, confirm: true }), opt-in; rows snapshotted, rollback-session restores
Safety and access
What can be undone on Gravity Forms, and what costs what.
Recoverable on Gravity Forms
- update-entry-status snapshots the single gf_entry row before the change.
- rollback-operation restores the previous status, whether it was active, spam or trash.
- update-notification, set-notification-recipients and update-confirmation snapshot the form's gf_form_meta row, and rollback-operation restores it.
- delete-entry snapshots every gf_entry, gf_entry_meta and gf_entry_notes row it removes in one session, and rollback-session puts the whole entry back.
- If the entry changed again in between, the restore warns instead of silently overwriting.
Gravity Forms limits and opt-ins
- Notification, confirmation and delete writes are off until the site opts in with the wpmcp_enable_forms_write filter.
- set-notification-recipients, update-confirmation and delete-entry need confirm:true.
- delete-entry removes the rows directly: Gravity Forms' gform_delete_entry action does not run, uploaded files stay on disk, and an entry with a payment is refused.
- Forms and fields are read only.
- Every entry operation and every write needs manage_options on top of the pair's own capability, because submissions are user data.
Free or Pro: Gravity Forms is part of the Pro forms pack, along with WPForms, Formidable, Ninja Forms and Fluent Forms. Without a Pro licence the gravityforms-read and gravityforms-write tools are not registered at all. The tools also appear only while Gravity Forms is active, so a site without it is not offered tools that could only fail. Any Gravity Forms licence level works because the integration uses the public GFAPI. The status move needs no opt-in; the notification, confirmation and delete writes do.
Part of WP MCP Pro
The Gravity Forms integration is part of WP MCP Pro.
One Pro licence unlocks the Gravity Forms tools and every other Pro integration on this site: Elementor deep editing, the other page builders, the forms adapter pack and more, 133 Pro tools in all. The free plugin still covers the rest of WordPress and the full snapshot and undo engine, so you can try the safety model before you buy.
Frequently asked
Gravity Forms MCP: questions, answered.
With Gravity Forms, can the agent delete entries?
Yes, once the site opts in with the wpmcp_enable_forms_write filter, and only with confirm:true. delete-entry removes the entry's gf_entry, gf_entry_meta and gf_entry_notes rows directly, so Gravity Forms' gform_delete_entry action does not run and uploaded files stay on disk. It is refused for an entry with a payment. Every row is snapshotted first and rollback-session puts them back, so a copy stays in the snapshot history until it is pruned: this is not a privacy erasure.
Can the Gravity Forms integration edit notifications and confirmations?
Yes, after the same opt-in. update-notification edits enabled, name, subject, message, sender and reply-to; set-notification-recipients changes the to and bcc and needs confirm:true; update-confirmation edits a confirmation's type, message, page or redirect and needs confirm:true. Each is undone with rollback-operation. Forms and fields themselves stay read only.
Is Gravity Forms part of the free plugin?
It is part of the Pro forms adapter pack, alongside WPForms, Formidable, Ninja Forms and Fluent Forms. It uses the standard GFAPI, so any Gravity Forms license level works.
Which entry statuses can it set?
Active, spam and trash, which are the states Gravity Forms' own entry list moves an entry between. Moving to trash is not a delete: the entry stays in gf_entry and can be moved back, or restored with rollback-operation. Permanent deletion is the separate delete-entry operation, which is opt-in and needs confirm:true.
Does the Gravity Forms integration include entry notes?
Yes, as a read. get-notes lists the notes attached to an entry, and get-entry returns all field values plus meta. Both need manage_options. There is no write for notes, so an agent can read the internal discussion on an entry but not add to it.
Can the Gravity Forms integration edit a form or a notification?
Notifications and confirmations, yes, once the site opts in: update-notification edits enabled, name, subject, message, sender and reply-to, set-notification-recipients changes the to and bcc, and update-confirmation edits the type, message, page or redirect. Each returns before and after and is undone with rollback-operation. Forms and fields stay read only, so changes to the form itself are made in the Gravity Forms editor.
How does paging work on large forms?
list-entries returns newest first with page_size (default 20, maximum 100) and an offset, plus an optional status filter of active, spam or trash. An agent working through thousands of entries pages through them in blocks instead of pulling the whole table in one response.
Is there an AI agent for Gravity Forms?
Yes, through WP MCP rather than Gravity Forms itself. An agent you choose, such as Claude or Cursor, can list forms with entry counts and field counts. WP MCP is a separate plugin, not a built-in AI feature of Gravity Forms. On the undo side: update-entry-status snapshots the single gf_entry row before the change.
Related integrations
More integrations for the same agent.
MCP for WPForms
ProForms, 5 tools.
MCP for Fluent Forms
ProForms, 6 tools.
MCP for Formidable Forms
ProForms, 6 tools.
MCP for Ninja Forms
ProForms, 5 tools.
MCP for Forminator
FreeForms, 5 tools.
MCP for WS Form
FreeForms, 2 tools.
Browse the full Integrations hub, or read more on Gravity Forms MCP and the WordPress MCP plugin.