Get the plugin
WP MCP/Integrations/Forms

Forms integration

Ninja Forms MCP

Ninja Forms stores forms and fields in its own models, reached through Ninja_Forms()->form(), and each submission as an nf_sub post. WP MCP Pro exposes them as a ninjaforms-read and ninjaforms-write pair: list forms, read fields and email notifications (Ninja Forms email actions), page through submissions without loading a form's whole history, and read one. update-entry-status moves a submission between active and the trash, the only two states Ninja Forms gives one, and because a submission is a post the write is snapshotted and restorable.

ninjaforms-readninjaforms-writelist-formslist-entriesupdate-entry-status

In practice

How Ninja Forms work goes with an agent.

Ninja Forms splits its data in two. Forms, fields and actions are models reached through Ninja_Forms()->form(), while every submission is an nf_sub post whose _form_id meta names its form, so a submission is a normal WordPress post with only two states: active and trash. WP MCP lists submissions by paging those posts instead of loading a form's whole history, reads email notifications as Ninja Forms email actions, and treats submissions as personal data, with every entry op needing manage_options. The writes move a submission to or from the trash and, once the site opts in, delete one.

What fields does the Contact form have, and which are required?

Runs list-forms to find the form id, then list-fields, which returns each field's id, key, type, label and whether it is required. get-form returns the same form with its field definitions. Reads only.

Where do the notification emails for form 8 go, and are they all switched on?

Runs list-notifications, which lists the form's email actions with label, active flag, recipient, subject and message template. Other action types, such as webhooks, are left out.

Show the newest 20 submissions on form 8, then read number 301.

Runs list-entries with page_size 20 and optionally status active or trash, then get-entry for the submitted values. Both need manage_options, since submissions are user data.

Trash yesterday's test submissions, and bring one back if I ask.

Runs update-entry-status with status trash, snapshotted as a post first. Setting status active later puts the submission back in the published state Ninja Forms lists, and rollback-operation also restores it.

What your AI can do

Real Ninja Forms operations, every write reversible.

  • List Ninja Forms forms and read their fields
  • Read a form's email notifications
  • Page through submissions and read a single one
  • Move a submission between active and trash, snapshotted and reversible
  • Delete a submission (opt-in, confirm:true, restorable with rollback-operation)

Example prompts

Example Ninja Forms prompts.

List my Ninja Forms and what fields each one has.

Summarize this week's submissions to the Contact form.

Trash the test submissions from yesterday.

Under the hood

The Ninja Forms calls, under the hood.

wpmcp, ninja-forms

ninjaforms-read({ operation: "list-entries", args: { form_id: 8, page_size: 20 } }), paged

ninjaforms-write({ operation: "update-entry-status", args: { entry_id: 301, status: "trash" } }), snapshotted, reversible

Safety and access

What can be undone on Ninja Forms, and what costs what.

Recoverable on Ninja Forms

  • update-entry-status snapshots the submission post (its row, meta and terms) before moving it.
  • rollback-operation restores it exactly, as does setting status active.
  • delete-entry snapshots the submission post and its meta first, and rollback-operation brings it back at its original id.
  • A move that changes nothing, such as trashing a submission already in the trash, returns changed:false and writes nothing.

Ninja Forms limits and opt-ins

  • delete-entry is off until the site opts in with the wpmcp_enable_forms_write filter and needs confirm:true. A snapshot copy stays until it is pruned, so it is not a privacy erasure.
  • update-entry-status is refused with trash_disabled when the site has the trash turned off (EMPTY_TRASH_DAYS is 0), because trashing would then delete the submission permanently.
  • Forms, fields and notifications are read only: no op creates a form or edits a notification.
  • Every entry op needs manage_options on top of the pair's own capability. The status move carries no opt-in filter of its own.

Free or Pro: Ninja Forms support is Pro, in the forms adapter pack, and registers only while Ninja Forms is active. It uses the standard Ninja_Forms() model API from the free Ninja Forms plugin, so no paid Ninja Forms add-on is needed. Everything here, reads and writes, needs a licensed WP MCP site and manage_options for entries. Deleting a submission additionally needs the site's opt-in and confirm:true.

Part of WP MCP Pro

The Ninja Forms integration is part of WP MCP Pro.

One Pro licence unlocks the Ninja 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

Ninja Forms MCP: questions, answered.

With Ninja Forms, can the agent permanently delete submissions?

Yes, once the site opts in with the wpmcp_enable_forms_write filter, and only with confirm:true. delete-entry snapshots the nf_sub post and its meta first, and rollback-operation brings it back at its original id. Moving to the trash is the gentler option. A snapshot copy stays until it is pruned, so a delete is not a privacy erasure.

Is the Ninja Forms integration part of the free plugin?

It is part of the Pro forms adapter pack, and uses the standard Ninja_Forms() model API in the core plugin.

Does the Ninja Forms integration load a form's whole submission history to list entries?

No. Ninja Forms' own submission loader reads every submission of a form with no paging, so list-entries pages the nf_sub posts directly, with page_size up to 100 (20 by default), an offset and a status filter, and loads values only for the rows it returns. A large form stays cheap to read.

Which notifications does list-notifications return?

Only Ninja Forms email actions, with their id, label, whether they are active, the recipient, subject and message template. Other actions on a form, such as a webhook or a mailing list connection, are not listed. An unset active flag is reported as on, which is how Ninja Forms treats it.

What if the site has the WordPress trash turned off?

Then update-entry-status refuses to trash with trash_disabled and writes nothing, because with EMPTY_TRASH_DAYS at 0 a trash would really delete the submission without a snapshot. Deleting is the separate, opt-in delete-entry, which snapshots first. Restoring a submission from the trash to active still works.

What does the agent see when a form id does not exist?

Ninja Forms' own model factory returns a form object for any id, so list-forms is used to check that the form exists. For an unknown id get-form returns a null form, list-fields a null field list and list-notifications a null notification list. Reading an unknown entry id returns a null entry.

Point your AI at Ninja Forms.