Developers

MCP for AI Agents

Connect a compatible AI assistant to your WordPress forms, entries and payments with 15 built-in tools.

Ask AI about this:

Built-in MCP · Free core feature

Let your AI assistant work with your WordPress forms

Connect a compatible MCP client to read entries, inspect payments and prepare form changes. Your forms and entries stay in WordPress; data returned to an assistant is shared with that client.

Read submissions without opening wp-admin

Prepare form changes before confirming them

Keep access controlled by WordPress permissions

See setup and tool reference

Example assistant workflows · illustrative, not a live connection

list_submissionsRead

Fetch submitted entries with an unread status. Your assistant can use the returned data to summarize the enquiries.

Write tools require a preview and a confirmation token. Review the change before allowing your client to confirm it.

What you can do

ChargeForms includes an MCP server in the free core plugin. A compatible client can read form definitions and submissions, inspect site payment totals, and prepare changes using tools rather than copy-pasted exports. MCP is disabled by default.

Example workflow: ask your assistant to list unread enquiries, review its summary, then prepare an internal note for a selected entry. Read tools fetch data; write tools first return a preview and a server-issued confirmation token.

Connect your site

Install ChargeForms and test a normal form submission first.
Open ChargeForms → Global Settings → Advanced → MCP for AI Agents and enable access.
Copy the endpoint shown in your settings. Its structure is https://your-site.com/wp-json/chargeforms/v1/mcp.
In your WordPress user profile, create a dedicated Application Password for the integration. Use HTTPS and an authorized user with the chargeforms_manage_forms capability.
Configure your MCP client with the endpoint and WordPress credentials using its supported authentication method. Client support and setup vary; an endpoint alone does not guarantee compatibility with every assistant.
Start with get_forms_context or list_forms. Test a read before allowing a write.

Do not paste application passwords into a chat or publish them. Revoke the dedicated application password when disconnecting an integration, and disable MCP when you no longer need it.

Read tools

Tool	Purpose
`get_forms_context`	Site overview of forms and entries
`list_forms`	Paginated form list
`get_form`	One form's definition and settings
`list_submissions`	Paginated submitted entries
`get_submission`	One entry's values and metadata
`get_form_stats`	Entry counts for one form
`list_integrations`	Available integrations and connection status
`get_payment_summary`	Site payment totals, optionally filtered by dates
`get_activity_log`	Recent site activity

Write tools

Tool	Proposed change
`create_form`	Create a form from a title and fields
`update_form_fields`	Replace a form's field list
`update_submission_status`	Change one entry's status
`bulk_update_submission_status`	Change multiple entry statuses
`delete_submission`	Permanently delete one entry
`add_submission_note`	Add an internal note to an entry

Write flow: request → preview → review → confirm. The second call must include the confirmation token for the same tool, arguments and WordPress user. A token requirement is a technical gate; configure your client to show the preview and ask you before confirming. Permanent deletion cannot be undone.

All tools use the WordPress user's chargeforms_manage_forms capability. This is broad management access, not a per-form or read-only permission. A connected client with those credentials can request the exposed write tools.

Entries remain stored in WordPress, but data returned by a tool is transmitted to your connected AI client. Review that provider's data handling and avoid sending unnecessary personal or sensitive submission data.

Troubleshooting

MCP not enabled: check the settings toggle on the site you are connecting.
Unauthorized: check the WordPress username, dedicated Application Password and user capability.
Client cannot connect: confirm it supports this server's HTTP transport and authentication method. Check your site's REST API and HTTPS access.
Confirmation required: inspect the preview, then let your client send the exact arguments with the returned token if you approve the change.

See the full tool guide for parameter examples, roles and permissions, or contact us for setup help.