Limited time discount
First Birthday, Big Savings
Up to 80%Off
Up to 80%Off
Grab Now
documentation-logo
IvyForms.com
Menu
  • Guides
  • Integrations

June 8, 2026

What is IvyForms MCP and how do I enable it

Imagine asking an AI assistant to “list my forms, then add a phone field to the contact form” and watching it happen without you clicking through the admin yourself. That’s what MCP (Model Context Protocol) brings to IvyForms; it lets an AI assistant work with your forms through conversational tools that run on the same REST API as the admin interface. The main in-product use is with Angie, Elementor’s AI assistant, which can call IvyForms tools while you’re in the WordPress admin. This article explains what MCP can do, how to switch it on, and where its limits are.

What do I need to use IvyForms MCP?

A few things have to be in place before MCP will work:

  • WordPress 6.9 or newer, which bundles the WordPress Abilities API that MCP relies on.
  • IvyForms installed and active.
  • An account with site administrator rights (the manage_options capability).
  • MCP turned on; it’s off by default and has to be enabled in settings.
  • For in-browser use, the Angie plugin active (WordPress 6.5 or newer); Angie is Elementor’s free AI agent, currently in beta.

The first time you activate Angie it sends you to an Elementor login, but that account is free to create, so you don’t need a paid Elementor license to use Angie with IvyForms. Angie runs on daily renewing credits during its beta.

How do I enable IvyForms MCP?

You enable MCP from IvyForms → Settings → General. Log in as a site administrator, turn on MCP integration, and save. Until it’s on, the MCP endpoint isn’t registered and any agent that tries to reach it gets a 404 (not found) error. For more on this screen, see the general settings documentation.

MCP integration toggle in IvyForms general settings

Developers can override the stored setting with the ivyforms/mcp/enabled filter to force MCP on or off, but the toggle in settings is the normal way to do it.

How does IvyForms MCP connect to Angie?

When Angie is active, IvyForms loads a small script on its admin screens that connects to the WordPress MCP endpoint at /wp-json/mcp/ivyforms-mcp-server and registers a server named IvyForms. From then on, when you ask Angie to manage your forms, it calls IvyForms tools that run through the same REST API as the admin interface, with the same permissions as your logged-in session. You need to be logged into WordPress in the browser for this to work, since the connection uses your admin session. If you’d rather drive IvyForms from an external assistant like Claude Desktop, Cursor, or Claude Code, that’s a separate and more technical setup; see the connecting an external MCP client documentation.

Angie assistant showing available IvyForms in the WordPress admin

What can the AI do once MCP is enabled?

With MCP on, the assistant can use a fixed set of tools across these areas:

  • Forms – list forms, open form details, create or duplicate forms, update settings and status, and add, reorder, or duplicate fields.
  • Entries – list entries, view a summary, count them, and star or unstar.
  • Notifications – list, view, create, update, duplicate, and search.
  • Settings – read only; view plugin settings, with sensitive values masked.
  • Templates – list and view available templates.
  • Integrations – list integrations and view their status.
  • Navigation – get admin links that jump you straight to the form builder or a specific entry.

What can't IvyForms MCP do?

MCP deliberately leaves some actions out, both for safety and for privacy:

  • No deleting – there are no tools to delete forms, entries, or notifications.
  • No saving settings – plugin settings are read-only over MCP.
  • No confirmation-message editor – confirmation flows aren’t exposed as tools.
  • Administrators only – subscribers, guests, and visitors can’t use MCP.
  • Submission data is masked – entry field values, IP addresses, user agents, and similar data are redacted in MCP responses; use the admin links to view full submissions in WordPress.
  • Secrets are masked – API keys, tokens, passwords, and SMTP secrets show up as masked values.

How do I keep IvyForms MCP secure?

Because the assistant acts with your own admin capabilities, treat the toggle with the same care as admin access:

  • Leave MCP disabled unless you’re actively using an AI assistant on that site.
  • Only enable it for trusted administrators.
  • Review any form changes the AI suggests before you publish them.
  • Never share application passwords used for MCP with anyone you don’t trust.

Enabling MCP gives the AI real edit access to your forms, fields, and notifications, not just read access. Switch it on knowing the assistant can change live form data.

Why aren't IvyForms tools showing up in Angie?

If Angie isn’t listing IvyForms tools, work through the usual culprits: confirm the MCP integration toggle is on, that you’re on WordPress 6.9 or newer, that the Angie plugin is active, and that you’re actually on an IvyForms admin page. A 404 on the MCP URL means MCP is still disabled in settings, and permission errors usually mean you’re not logged in as a site administrator. If tools went missing right after a deploy, the front-end build may not have run, so the bridge script isn’t present.