Get Forms Context is a WordPress ability from Fluent Forms — usable via Easy MCP AI, which connects Claude, ChatGPT, and any AI assistant to your site.
Install Free Plugin →Get Forms Context
Read-onlyLoad the caller's permissions, the site's valid status enums, headline stats, and the accessible forms list in one call.
Needs the Fluent Forms MCP server switched on in FluentForm → Settings → MCP, and WordPress 6.9+ so wp_register_ability() exists (abilities are only registered when the function is present). Reaching the server also requires a logged-in WordPress user holding at least one FluentForm capability. Each ability additionally checks a specific FluentForm capability (e.g. fluentform_dashboard_access, fluentform_forms_manager, fluentform_entries_viewer, fluentform_manage_entries, fluentform_view_payments, fluentform_settings_manager) via the plugin's own Acl system, and every write ability requires a two-step dry_run → confirm_token round-trip through WriteGuard before anything is persisted. Note (from source comments): a WordPress role granted FluentForm access via the Role Manager passes every per-ability capability check, including delete-submission and bulk delete_permanently — the real boundary for such a user is 'has FluentForm access, restricted to their form scope', not per-tool separation; only individually-assigned 'specific forms' managers are gated the way each ability's declared capability implies.
What it does
This is FluentForm's documented "call this first" tool — the single entry point an agent should use before anything else. It returns who the caller is (WordPress user id, name, email, admin flag, and the FluentForm permissions actually granted), basic site info (name, url, FluentForm version, whether Pro is active, timezone), headline stats (forms_total, submissions_total, submissions_last_30d), a compact list of up to 50 forms the caller can access (id, title, status, type), the authoritative enum values for submission_statuses, form_statuses, and note_statuses, and a guidelines block explaining the required dry-run/confirm_token pattern and how untrusted form content is fenced. The response is cached per user for 60 seconds and invalidated automatically when forms or permissions change; unrestricted-scope headline counts additionally share a 15-minute cache since they are identical for every unrestricted admin. Calling this first means the agent never has to guess a status string or a form id.
See it in action
You ask your AI assistant
"Give me an overview of what I can do with Fluent Forms on this site and how many submissions came in this month."
Returns
An envelope with a summary message and data containing: you (wp_user_id, name, email, is_admin, permissions granted), site (name, url, version, pro_active, timezone), stats (forms_total, submissions_total, submissions_last_30d), forms (up to 50 accessible forms: id, title, status, type), enums (valid submission_statuses, form_statuses, note_statuses), and guidelines (usage instructions for the agent).
Permission
Requires at least one FluentForm role capability: fluentform_dashboard_access, fluentform_forms_manager, fluentform_entries_viewer, fluentform_view_payments, or fluentform_settings_manager (any one is enough).
More Fluent Forms abilities
Add Submission Note
Attach an internal staff note to one entry; not visible to the submitter.
Bulk Update Submissions
Apply one action — read, unread, trashed, favorite, unfavorite, or permanent delete — to up to 200 entries at once.
Create Form
Create a new form from a title and an ordered list of fields, or a basic contact form by default.
Create or Update Email Notification
Create a new email notification or update an existing one — including its recipient.
Delete Submission
Permanently delete one entry and its uploaded files.
Get Form
Load one form's full detail, including its field schema, so the agent knows the exact field keys used in submissions.