A brief becomes a real page.MetForm MCP integration
Connect the MetForm layout to the entries it collects.
EMCP Pro reads MetForm fields from their Elementor layout and exposes stored submissions for review. Inspect the form people see, understand its inputs, and review the values returned by its entries.
Pro integrationMetForm + Elementor active
Connect the Elementor form layout to its submissions.
| Workflow detail | What to check |
|---|---|
| Elementor form layout | Discover MetForm inputs |
| Stored submission | Map values to field labels |
| Rendered form | Check the visitor-facing layout |
| Test entry | Review before confirmed cleanup |
A practical place to start
Connect the Elementor form layout to its submissions.
- 01
Read the saved form layout
Inspect the MetForm fields parsed from its Elementor structure. Identify the inputs in the enquiry form before trying to interpret any stored submission.
- 02
Match answers to inputs
Retrieve the selected submissions and map their values to the returned fields. Keep both the form and submission identifiers in the review so layout and entry evidence remain connected.
- 03
Check the published form
Preview the rendered form and test a submission when investigating a mismatch. If a test entry needs removing, use the separate confirmed deletion operation for that specific record.
Built for MetForm
Start where MetForm defines its fields
MetForm’s connection to Elementor makes layout context useful. The adapter parses fields from the saved Elementor structure rather than assuming a generic form schema. Inspect the enquiry form’s field list, then match those fields to the returned submission values. Keep the saved layout and submitted data visible as separate parts of the review.
Keep layout work and entry work distinct
The integration reads form data and can delete a submission with confirmation. It does not become a complete MetForm builder simply because Elementor tools are also available on the site. Any separate layout change needs its own verified Elementor workflow, followed by an actual submission check on the rendered form.
Keep design review and entry review connected
An enquiry can look different in the form layout and in a stored record. Inspect both before deciding that a field is missing or that an answer was not collected. If the page design needs adjusting, use a verified Elementor workflow for that layout, then test the actual form again. The entry adapter supplies the record inspection and cleanup tools; the rendered submission flow remains the final check for how the form behaves.
Read the MetForm tool documentation for the supported operations and parameters.
Choose by the work you need to do
MetForm MCP integrations, compared.
Compare the documented workflows in EMCP, Novamira, Respira, and WPVibe. A general code or API route may offer more than a dedicated integration documents.
Checked · Documentation review, not a hands-on benchmark. “Unverified” means the reviewed sources do not establish that capability; it does not mean unsupported. Editions and installed versions may affect availability.
Scroll horizontally to compare all four products. Each source number opens the supporting documentation.
| Workflow | EMCPOur integration | Novamira | Respira | WPVibe |
|---|---|---|---|---|
| Discover fields from Elementor | Dedicated layout parsing [1] | No specific coverage verified [2] | No specific coverage verified [3] | General access; exact task unverified [4] |
| Read submissions | Dedicated entry reads [1] | General access; exact task unverified [2] | No specific coverage verified [3] | General access; exact task unverified [4] |
| Delete submission | Confirmed delete [1] | General access; exact task unverified [2] | No specific coverage verified [3] | General access; exact task unverified [4] |
| Author MetForm structure | Outside adapter [1] | General code only; unverified [2] | General builder only; unverified [3] | General Elementor only; unverified [4] |
Sources & comparison methodology
We compare specific tasks, including EMCP’s limits. Vendor documentation describes advertised support; it does not prove identical behavior, reliability, or performance. Broad API access is distinguished from a documented integration workflow. No scores or tool counts determine a winner.
Get connected
Put MetForm in your AI’s toolkit.
- 1
Prepare the integration
Activate Elementor, MetForm, and EMCP Pro on the same site. Start with a saved MetForm layout and inspect its parsed fields before selecting submissions to review.
- 2
Check the available tools
Connect your MCP client to this WordPress site and check metform-read / metform-write in EMCP’s tool settings. Inspect the live operation catalog before starting the MetForm workflow; installed plugins, editions, and saved tool choices determine what is available.
- 3
Establish a first test
Choose an existing MetForm form and inspect its parsed fields alongside a known submission. Confirm the target entry belongs to that form before considering a deletion operation.
Then connect Claude Code, Claude Desktop, or Cursor to use the MetForm tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about MetForm, supported operations, and the workflow on your site.
Does MetForm require Elementor?
Yes. The integration depends on MetForm’s Elementor-based setup.
Can this recreate a MetForm from a prompt?
Form-structure authoring is outside this adapter. Use its field and entry reads to inspect the existing setup.
Where does the field list come from?
The adapter parses the saved Elementor layout used by MetForm. That field list and the stored submission values are distinct sources in the review.
Does it manage MetForm payment settings?
Payment administration is not part of the documented form-and-entry adapter. Verify any separate workflow before relying on it.
Your tools. Your WordPress site.