Get the plugin
WP MCP/Integrations/Forms

Forms integration

Contact Form 7 AI agent tool reference

Contact Form 7 stores forms through the WPCF7_ContactForm model and, by design, does not store submissions itself; Flamingo does that. WP MCP exposes both, free: list forms, read a form's markup, fields and mail templates, and, when Flamingo is active, list and read stored submissions, move one between the inbox and the trash, or delete one. Entry operations need edit_users, the capability Flamingo itself maps its screens to. Because a Flamingo entry is an ordinary post, the status move and the delete are snapshotted first and rollback-operation restores them.

contactform7-readcontactform7-writelist-formsget-formlist-entries

In practice

How Contact Form 7 work goes with an agent.

Contact Form 7 has two halves, and an agent needs to treat them differently. Forms are stored by the plugin: the markup you write in the form editor and two mail templates, the notification and an optional autoresponder. Submissions are not stored by Contact Form 7 at all. If Flamingo is installed, it saves each one as a post in its own inbound message type. WP MCP reads the forms side freely and puts the submission side, which is personal data, behind the capability Flamingo itself uses.

Who does the Quote form email, and does it send an autoresponder?

Runs list-notifications for the form, which returns the primary Mail template and the optional Mail (2), each with whether it is active, recipient, sender and subject. Read only.

Which fields on the Contact form are required, and what types are they?

Runs list-fields, which lists name, type, required flag and options as Contact Form 7 parses them from the markup. get-form returns the raw markup if you want to compare.

List the five newest Quote submissions with their subjects.

Runs list-entries with form_id, a page size of 5 and the default inbox status, then get-entry for full values. It needs Flamingo and the edit_users capability. Without Flamingo it answers flamingo_unavailable.

Move submission 88 to the trash, it is spam.

Runs update-entry-status with status trash through Flamingo's own trash method. The entry is snapshotted first, and rollback-operation restores it. If the site has the trash disabled the op refuses rather than deleting.

What your AI can do

Real Contact Form 7 operations, every write reversible.

  • List Contact Form 7 forms with title and slug
  • Read a form's field markup and mail template (recipients, subject, body)
  • With Flamingo: list and read stored submissions
  • With Flamingo: move a submission between inbox and trash, reversibly
  • With Flamingo: delete a submission (opt-in, confirm:true, restorable)

Example prompts

Example Contact Form 7 prompts.

Show me the mail template for the Contact form, who does it email?

List the last 20 submissions Flamingo stored for the Quote form.

Move the obvious junk submissions to the trash.

Under the hood

The Contact Form 7 calls, under the hood.

wpmcp, contact-form-7

contactform7-read({ operation: "get-form", args: { form_id: 7 } }), markup + mail

contactform7-write({ operation: "update-entry-status", args: { entry_id: 88, status: "trash" } }), needs Flamingo; snapshotted

Safety and access

What can be undone on Contact Form 7, and what costs what.

Recoverable on Contact Form 7

  • update-entry-status is snapshotted as a post and undone with rollback-operation.
  • delete-entry, when a site has enabled it, is snapshotted too (row, meta and terms) and can be restored at its original id.
  • Restoring a submission needs edit_users, the same capability as reading it.

Contact Form 7 limits and opt-ins

  • Forms are read only. There is no operation that edits a form, its markup or its mail templates.
  • delete-entry is off until a site opts in with the wpmcp_integration_op_enabled filter and needs confirm true.
  • A delete is not a GDPR erasure: the snapshot keeps a plaintext copy until it is pruned.
  • Status is limited to inbox and trash. Spam flagging is not offered because Flamingo would report it to Akismet.

Free or Pro: All of this is in the free plugin. Form reads (list-forms, get-form, list-fields, list-notifications) need no extra plugin. Submission ops (list-entries, get-entry, update-entry-status and delete-entry) need Flamingo active and the edit_users capability. Moving an entry between inbox and trash is on by default; deleting is destructive and stays off until a site enables it. Pro adds a separate forms adapter pack for other form plugins, not for Contact Form 7.

In the free plugin

The Contact Form 7 integration is in the free plugin.

The core Contact Form 7 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

Contact Form 7 MCP: questions, answered.

Can I read Contact Form 7 submissions?

Yes, when Flamingo is active. Contact Form 7 itself stores none, so without Flamingo the entry operations answer flamingo_unavailable and the form reads keep working.

Is deleting a submission a GDPR erasure?

No, and the op says so. The delete is off until a site opts in, needs confirm:true, and is snapshotted so it can be restored, which means a copy of the submission stays in the snapshot history until it is pruned. Restoring it needs edit_users.

Why is spam flagging not offered?

Flamingo reports spam to Akismet, which would send the submission to a third-party service. The status move is limited to inbox and trash.

Why does it need edit_users and not manage_options?

Because Flamingo maps its inbound message capabilities to edit_users. On multisite, core turns that into a super admin capability, whereas manage_options would let an ordinary site administrator read submissions that Flamingo's own screens deny them. WP MCP follows the stricter rule on purpose.

How are submissions matched to a form?

list-entries takes a form_id and resolves it to the form's Flamingo channel. A form whose channel binding is missing is refused, not answered with an unscoped list of every submission. You can filter by inbox, spam or trash and page up to 100 at a time.

With Contact Form 7, can the agent see mail recipients and bodies?

Yes. list-notifications and get-form return the Mail template with recipient, sender, subject and body, including mail tags. Those are configuration, not submissions. A site that treats recipient addresses as confidential should keep the agent user's role narrow.

Does reading a submission mark it as read or change it?

No. list-entries and get-entry are read only and nothing is written, so no snapshot is taken. Only update-entry-status and delete-entry change a Flamingo post, and both are snapshotted before they run.

Point your AI at Contact Form 7.