What is an MCP Server?
Your Gravity Forms MCP Server enables AI assistants as well as other MCP-compatible clients to read and manage your Gravity Forms, including forms, entries, and feeds. It uses the Model Context Protocol (MCP), a standardized framework that connects AI tools to your WordPress site and exposes Gravity Forms functionality as discoverable, executable tools.
Instead of manually describing your form structure to an AI assistant, your MCP Server lets the AI access, analyze, and work with your forms directly. It is a bridge between your forms and AI.
⚠️ Note: The MCP (Model Context Protocol) integration lets AI assistants access your Gravity Forms, including reading, creating, updating, and deleting forms, entries, and settings (including API keys). AI assistants can make mistakes. Enable write access only when necessary, validate outputs, maintain regular site backups, and consider how your AI assistant will have access to form-collected data.
This functionality requires WordPress 6.9 or higher (with the Abilities API) and self-hosted WordPress only. WordPress.com is not supported at this time.
Why Use It?
AI-Assisted Form Creation
Ask an AI to build a contact form, job application, or multi-step survey. The AI understands your requirements and creates the form directly in Gravity Forms.
Entry Analysis & Insights
Have an AI analyze form submissions, identify patterns, summarize data, or generate reports without manual exports or spreadsheets.
Automation & Workflows
Automate repetitive tasks: validate submissions, populate entries, trigger notifications, or manage feeds for PayPal, Stripe, Mailchimp, and other integrations.
Form Troubleshooting
Ask an AI to review your form configuration, check for missing fields, validate conditional logic, or suggest improvements.
Content Generation
Generate form field descriptions, help text, or placeholder copy based on your form’s purpose.
How It Works
Discovery
When you connect an AI tool to your Gravity Forms site, the MCP Server exposes a catalog of available tools: get forms, list entries, create forms, update entries, submit forms, manage feeds, and more.
Execution
The AI tool can discover what it needs and call the appropriate tools with the necessary parameters. For example, if you ask an AI to “list all unread submissions from my contact form”, the AI calls the list-entries tool with the right filters.
Permission Enforcement
Every action respects your WordPress user’s capabilities and the MCP Server settings you’ve configured. An AI authenticated as a read-only user can only read forms and entries: it cannot create, update, or delete any forms or entries.
Connecting to your MCP Server
Refer to the Connecting to the MCP Server article for more information.
Key Capabilities
Read-Only Tools
View forms, entries, submissions, feeds, notifications, field types, and site information.
Write & Destructive Tools
Create, update, and delete forms and entries. These tools require careful permission management since an AI can modify or delete your data. Always review AI-suggested changes before applying them, especially on live sites.
Security & Permissions
Note: An MCP client gets the same reach into Gravity Forms as the account it authenticates as. Use a dedicated WordPress user scoped to the narrowest capabilities the task needs, not your own account. Refer to Creating a User for MCP Access for more information.
WordPress User Capabilities
The AI assistant connects as a WordPress user (via an application password). It can only perform actions that the user is allowed to do. If the user can’t edit forms, neither can the AI.
MCP Server Settings
You separately enable or disable specific tools. Even if a user has the capability to delete forms, you can disable the delete-form tool entirely in the MCP Server settings.
Opt-In Model
The integration uses a default-deny approach. Nothing is exposed until you enable each tool individually. There is no “all on” default state.
Best practice: Create a dedicated WordPress user with minimal capabilities (e.g., read-only access for AI-assisted analysis) and an application password for each MCP connection. Never use your admin account.
Use Cases and Sample Prompts
Refer to the MCP Use Cases and Sample Prompts for scenarios and example prompts you can adapt to your own forms.