# Gravity Forms MCP

> Gravity Forms MCP gives your AI agent full control over WordPress form submissions. You can list all forms on a site, pull specific entry data, update old records, or even programmatically submit new leads—all through natural conversation with your preferred client.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** form-builder, lead-capture, data-entry, wordpress-plugin, submission-management, rest-api

## Description

Connect this MCP to any compatible AI client and take charge of your entire Gravity Forms setup. Your agent can now manage everything related to form entries and submissions without you having to log into the WordPress admin dashboard. Want to know what forms exist? You can list them all and inspect their field structures. Need to track a specific customer? Retrieve detailed submission records, or update an old entry's values if the client changed their mind. If your team needs context on a tough case, you can read and even add internal notes directly to the submission record. It also lets you look at aggregate results for any form, so you can analyze conversion rates right in the chat window. We built this integration into Vinkius so you connect once and get access to all your data management tools.

## Tools

### create_entry_note
Attaches a private note to a specific submitted form entry for internal team context.

### delete_entry
Permanently removes an entire form submission record from the site database.

### get_entry
Fetches all detailed information and field values for one specific form entry.

### get_form_results
Retrieves aggregate statistics, helping you analyze the overall performance of a particular form.

### get_form
Provides the complete structure and configuration details for a specific form ID.

### get_notifications
Checks which external services are receiving notifications when a form is submitted.

### list_entries
Pulls a list of all submissions across the site, allowing you to narrow down results by date or criteria.

### list_entry_notes
Retrieves all internal notes that have been attached to a specific form entry ID.

### list_feeds
Lists the active data feeds connected to a specific form, ensuring external services are getting data.

### list_forms
Retrieves a list of every single form configured within your Gravity Forms site.

### submit_form
Submits new data to a specific form programmatically by passing in the required field values.

### update_entry
Modifies an existing, saved form entry record with new data.

## Prompt Examples

**Prompt:** 
```
List my forms in Gravity Forms
```

**Response:** 
```
Retrieving your forms... I found 3 active forms: 'Contact Us' (ID: 1), 'Service Request' (ID: 2), and 'Customer Feedback' (ID: 3). Would you like to see the entries for the service request form?
```

**Prompt:** 
```
Show me the entries for Form ID 1 from this week
```

**Response:** 
```
Fetching entries... I found 5 new submissions this week for the 'Contact Us' form. The latest is from John Doe (Entry #1042). Would you like to read the details of his message?
```

**Prompt:** 
```
Add a note to entry #1042: 'Customer contacted support, refund processed'
```

**Response:** 
```
Adding note... Success! I've added the internal note to Entry #1042. It is now visible to the support team in your WordPress dashboard.
```

## Capabilities

### List available forms
You retrieve a list of every form created on the site, including their IDs.

### Get form structure and settings
The agent reads the specific fields and configuration details for any given form ID.

### Retrieve all submissions
You pull a list of submitted entries across multiple forms, allowing you to search by date or criteria.

### Get specific entry data
The agent fetches the full details and field values for one specific form submission.

### Update existing entries
You modify specific fields in a submitted form record, correcting errors or adding missing information.

### Add internal notes to submissions
The agent attaches private, visible context notes to a submission for the support team's records.

### Analyze form performance metrics
You pull aggregate statistics and results to track how well a particular form is performing over time.

## Use Cases

### A customer calls with a billing question, but the original form entry is old.
Instead of making the agent ask for an ID and then searching by date, you simply tell it: 'Find me the submission for Jane Doe from last month.' The agent uses `list_entries` and `get_entry` to pull up the exact data needed immediately so the support team can process the refund.

### The marketing team needs to know which service request type is failing most often.
You ask your agent to analyze performance. It uses `get_form_results` on the 'Service Request' form, quickly identifying that 70% of submissions fail validation because a required field was missed—a stat you wouldn't get easily otherwise.

### The web admin needs to confirm if a third-party CRM is receiving new leads.
You instruct your agent: 'Check the feeds for the Contact Us form.' It uses `list_feeds` and confirms that the connection is active, validating data flow before launching a major campaign.

### A bug report comes in saying a submission was lost.
You ask your agent to confirm all submissions for Form ID 3 from last Tuesday. The agent uses `list_entries` and finds the missing record, confirming it was simply buried under thousands of other entries.

## Benefits

- Instead of logging into WordPress to check submissions, your agent handles it. You can instantly retrieve specific entry data using the `get_entry` tool and analyze who submitted what without manual searching.
- Support teams save hours by centralizing context. Use the `create_entry_note` tool to add internal notes right alongside the customer's submission, keeping a perfect record for faster resolution.
- Marketing analysis becomes instant. With one call to `get_form_results`, you pull aggregate statistics and conversion data—no need to export CSVs or build custom reports in Google Sheets.
- You can test submissions safely. Use the `submit_form` tool to programmatically trigger a form submission, running validation checks without needing to physically fill out a browser form first.
- System auditing is simple. The agent lets you list all forms (`list_forms`) and check their configuration (`get_form`), ensuring no critical fields or settings were accidentally changed.

## How It Works

The bottom line is that your AI client handles all API calls and data retrieval, letting you manage forms without touching a browser.

1. First, subscribe to this MCP on Vinkius and provide your Site Base URL, Consumer Key, and Consumer Secret from your WordPress Gravity Forms settings.
2. Next, tell your AI client exactly what you need. For example: 'List all forms and then check the submissions for Form ID 5.'
3. Finally, the agent executes the required actions—retrieving data, updating records, or calculating statistics—and presents the results back to you directly in the chat.

## Frequently Asked Questions

**How do I list all my forms using Gravity Forms MCP?**
You use the `list_forms` tool to get a complete catalog of every form on your site. This immediately gives you all the Form IDs necessary to work with them.

**Can I update an entry's data using Gravity Forms MCP?**
Yes, use `update_entry`. You need two things: the unique Entry ID of the record and the specific field values you want to change. This prevents accidental modification.

**Does Gravity Forms MCP only handle new submissions?**
No, it handles the entire lifecycle. You can list old entries using `list_entries`, retrieve details with `get_entry`, and even delete records entirely using `delete_entry`.

**What is the difference between getting an entry and listing submissions?**
Using `list_entries` gives you a high-level summary of many entries, like a quick table view. Using `get_entry` drills down to show every single field value for one specific submission.

**How do I document context for the support team using Gravity Forms MCP?**
You use the `create_entry_note` tool. This attaches a private, internal note that is visible to your team but won't appear in the submission data itself.