---
title: "GravityKit MCP tools reference"
date: 2026-08-17
author: "Block MCP (service account)"
link: "https://www.gravitykit.com/docs/gravitykit-mcp/available-tools/"
---

GravityKit MCP exposes two independent sets of tools. The **Gravity Forms tools**, named with a `gf_` prefix, are always present when your Gravity Forms credentials work. The **GravityKit product tools** are generated at runtime from the connected site, so which ones exist depends on the GravityKit products installed there.

The two are independent. A site with only Gravity Forms lists just the `gf_` tools; a GravityKit site without Gravity Forms REST credentials still lists its product tools.

You never type these names. They are what your assistant sees and chooses between when you describe what you want. Knowing them helps when you want to be specific (“use the validation tool, don't submit it”) or when you are reading back what the assistant did.

## Gravity Forms tools

### Forms

- `gf_list_forms` — list forms, optionally limited to specific IDs.
- `gf_get_form` — read a form's complete configuration.
- `gf_create_form` — create a form, with fields.
- `gf_update_form` — update an existing form.
- `gf_delete_form` — move a form to Trash, or delete it permanently with `force`. Requires `GRAVITY_FORMS_ALLOW_DELETE=true`.
- `gf_validate_form` — validate form data without saving anything.

### Entries

- `gf_list_entries` — list and search entries. Supports pagination, sorting, field filters with `any`/`all` matching and operators including `IN` and `NOT IN`, fetching by ID, exclusions, status, and querying several forms at once.
- `gf_get_entry` — read a single entry.
- `gf_create_entry` — create an entry.
- `gf_update_entry` — update an entry.
- `gf_delete_entry` — move an entry to Trash, or delete it permanently with `force`. Requires `GRAVITY_FORMS_ALLOW_DELETE=true`.

### Fields

- `gf_add_field` — add a field, positioned where you ask for it.
- `gf_update_field` — update a field, checking first for conditional logic that depends on it.
- `gf_delete_field` — delete a field, with the same dependency check.
- `gf_list_field_types` — list the 46 field types the server carries definitions for, with the storage format each one uses.

Field types added by other plugins work too. They are created normally, though the server has no built-in defaults or sub-inputs for them, so a custom compound or choice field needs its `inputs` or `choices` supplied explicitly.

### Submissions

- `gf_submit_form_data` — submit a form with full processing, the same as a visitor submitting it.
- `gf_validate_submission` — check a submission against the form's validation rules without creating an entry.

### Add-on feeds

Feeds are how Gravity Forms add-ons — Mailchimp, Stripe, PayPal, and the rest — decide what happens when a form is submitted.

- `gf_list_feeds` — list feeds.
- `gf_get_feed` — read one feed's configuration.
- `gf_create_feed` — create a feed.
- `gf_update_feed` — replace a feed's configuration.
- `gf_patch_feed` — change individual feed properties.
- `gf_delete_feed` — delete a feed. Requires `GRAVITY_FORMS_ALLOW_DELETE=true`.

### Notifications and results

- `gf_send_notifications` — send an entry's notifications, either specific ones or all notifications for an event.
- `gf_get_field_filters` — list the filters available for a form, which is what makes a precise entry search possible.
- `gf_get_results` — aggregated results for Quiz, Poll, and Survey forms.

## GravityKit product tools

When GravityKit Foundation is active on the connected site, GravityKit products publish their capabilities as “abilities” through Foundation and the [WordPress Abilities API](https://developer.wordpress.org/apis/abilities-api/). The server reads that catalog when it starts and turns each ability into a tool, so the exact set depends on which products and versions are installed. Each add-on gets its own prefix.

**GravityView** is supported today, under the `gv_` prefix. Its tools cover the View lifecycle (creating a View, applying a configuration, deleting it), field, widget, search, and grid editing, and discovery calls that report what layouts and field types the site offers. Setup and examples are in [Creating Views with AI using the GravityKit MCP](/docs/gravityview/advanced/build-views-with-ai/).

Because both sets are available at once, you can create a form and build a View for it in a single conversation.

One more tool sits outside both sets: `gk_reload_abilities` re-reads the GravityKit catalog. Ask your assistant to reload abilities after you activate or update a GravityKit product, and its tools appear without restarting the app.

Not sure what your site offers? Ask the assistant directly — *“What GravityKit tools do you have?”* It reports the catalog it actually loaded, which is more reliable than any list written down here.