Forms integration
MCP for Contact Form 7
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.
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
Just ask.
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 real calls.
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
Frequently asked
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.
More integrations
MCP for Gravity Forms
ProRead Gravity Forms forms, fields, notifications and entries over MCP, and move entries between active, spam and trash, undoably.
MCP for Formidable Forms
ProRead your Formidable forms, fields, email notifications and entries over MCP through Formidable's own models.
MCP for WPForms
ProRead WPForms forms, fields, notifications and entries over MCP, and move entries between active, spam and trash, undoably.
MCP for Ninja Forms
ProRead Ninja Forms forms, fields, email actions and submissions over MCP, and trash or restore submissions, undoably.
MCP for Fluent Forms
ProRead Fluent Forms forms, fields, notifications and submissions over MCP, and change a submission's status, undoably.
MCP for Forminator
FreeRead Forminator forms and submissions over MCP through its own API, free.