FunnelKit MCP integration
Understand your FunnelKit checkout before you change it.
Inspect saved funnels, step order, checkout products, and checkout fields through the FunnelKit MCP integration in EMCP Pro. Get a concise overview or the full saved page configuration when you need more detail. This integration is read-only in EMCP 3.16.0.
Pro integrationFunnelKit Funnel Builder active
Follow the saved checkout configuration
| Inspection sequence | What to read |
|---|---|
| 01 · Funnel | Saved step order |
| 02 · Checkout step | Products & quantities |
| 03 · Checkout fields | Required fields & order |
| 04 · Full page detail | Settings & design configuration |
A practical place to start
Turn a checkout question into a concrete inspection.
- 01
Locate the funnel
List or search the saved funnels, then read the chosen funnel’s ordered steps. Use the returned checkout step ID instead of assuming the first page is the checkout.
- 02
Read the checkout details
Retrieve configured products, quantities, discounts, and fieldsets for that step. Preserve the saved field order and identify required or custom inputs in the review.
- 03
Hand off the findings
Summarize the saved configuration with its funnel and step IDs. Request full page detail if the summary leaves a question unanswered, then make any intended edits in FunnelKit.
Built for FunnelKit
See how the funnel is actually arranged
A checkout review starts with the funnel and the steps saved inside it. Ask your assistant to list the sequence and identify the checkout step you want to inspect. It can then explain the products, quantities, and configured discounts for that step. Use the saved configuration as evidence rather than treating a funnel’s name as a reliable description of what it does.
Inspect the fields that shape the checkout
Required fields, custom inputs, and their saved order affect the form shoppers encounter. Read the checkout fieldsets and turn them into a plain-language review. When a summary does not answer the question, request the full decoded page configuration. Use those findings to plan the next change in FunnelKit. Funnel editing, contact management, and conversion statistics are outside this adapter.
A useful handoff between store and page teams
A checkout question can involve WooCommerce product records, a FunnelKit step, and an Elementor design. Read each from the tool that owns that information. The WooCommerce integration can inspect the catalog; FunnelKit reads the checkout’s configured products and fields; Elementor tools can inspect a supported page layout.
That gives the next person a more actionable brief: the funnel ID, the checkout step, the saved products, the required fields, and the page configuration that needs review. Keep observations about configuration separate from assumptions about shopper behavior. A field being required is a saved setting; whether it caused abandonment needs additional evidence.
Use the FunnelKit tool reference for operation names and request details. After making a change in FunnelKit, repeat the inspection and test the checkout itself to verify the intended result.
Choose by the work you need to do
FunnelKit 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 |
|---|---|---|---|---|
| List funnels and step order | Dedicated read operations [1] | No specific coverage verified [2] | No specific coverage verified [3] | No specific coverage verified [4] |
| Inspect checkout products | IDs, quantities, discounts and prices [1] | General access; exact task unverified [2] | General access; exact task unverified [3] | General access; exact task unverified [4] |
| Inspect checkout fields | Saved fieldsets and required fields [1] | General access; exact task unverified [2] | General access; exact task unverified [3] | General access; exact task unverified [4] |
| Full saved page configuration | Read summary or decoded full detail [1] | No specific coverage verified [2] | No specific coverage verified [3] | No specific coverage verified [4] |
| Edit funnels / Automations / analytics | Outside EMCP 3.16.0 adapter [1] | No specific coverage verified [2] | No specific coverage verified [3] | No specific coverage verified [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 FunnelKit in your AI’s toolkit.
- 1
Activate Funnel Builder
Install EMCP Pro 3.16 or later alongside FunnelKit Funnel Builder. This integration concerns Funnel Builder, not the separate FunnelKit Automations product.
- 2
Connect an authorized account
The connected WordPress user needs manage_woocommerce. Requests also pass through FunnelKit’s endpoint permissions.
- 3
Discover and inspect
Call funnelkit-read to discover the operations. Begin with a small funnel list, select a returned funnel ID, and then inspect the checkout step returned by that funnel.
Then connect Claude Code, Claude Desktop, or Cursor to use the FunnelKit tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about FunnelKit, supported operations, and the workflow on your site.
Can I create or edit funnels with this integration?
No. EMCP 3.16.0 exposes FunnelKit reads only. Enabling another write tool does not add FunnelKit editing.
Does it connect to FunnelKit Automations?
No. Automations, contacts, and conversion statistics are outside this Funnel Builder inspection surface.
Can it show the full page configuration?
Yes. Discover the step ID first, then request get-funnel-page with detail set to full. The smaller summary is useful for routine checks; full detail returns the decoded saved configuration.
Can it explain why conversion rates dropped?
It can help review the saved checkout configuration, but it does not provide conversion statistics or session evidence. Bring analytics and actual checkout observations into a separate investigation.
Your tools. Your WordPress site.