LocalForm registers three WordPress Abilities - list forms, read a form, create or update one - and the MCP Adapter turns them into tools an assistant such as Claude can call. The assistant connects to your WordPress. Nothing about your site or your responses is uploaded anywhere.
Set it up Download freePart of the free plugin. Needs WordPress 6.9 or newer and the MCP Adapter.
One sentence, and the form is on your site waiting for you to look it over.
Make a registration form for the summer school on 12 and 13 August, in the main hall, €80 for adults and €40 for students. Cap it at 60 people and close it on 5 August.
Built it on your site and left it for you to check.
localform/save-form — six questions, two event dates, two rates, a maximum
of 60 and a closing date of 5 August.
Your assistant reaches into your WordPress and calls an ability there. LocalForm opens no connection of its own, and no form or response is shipped to a vendor for processing.
The abilities run as the signed-in user and require the same permission the builder screen does. Remote clients authenticate with an Application Password you issue and can revoke.
Everything goes through the same validation as the builder, so an assistant cannot save a form you could not have made by hand.
Reconfiguring a form leaves the answers it has already collected exactly as they were - and the abilities do not expose those answers in the first place.
These are WordPress Abilities, registered the way core intends. Any MCP client that can reach your site works; nothing here is specific to one assistant.
LocalForm Pro adds a Build with AI panel that drives the same abilities from within WordPress - no client, no bridge, no Application Password.
The Abilities API ships in core from 6.9. Below that LocalForm registers nothing - the rest of the plugin still works from 6.5.
It turns registered abilities into MCP tools. Install the release zip rather than a zip of the
branch; the branch has no vendor/ and registers no endpoint.
Generated under Users → Profile, for the account the assistant should act as. Revoke it and the connection is gone.
The setup guide walks through it with screenshots, including what each failure message means.
The assistant connects to your WordPress; LocalForm sends nothing out. What the assistant sees is what it asks for through the abilities - the forms you point it at. Responses people have submitted are not exposed by these abilities at all.
Nothing. The three abilities are part of the free plugin. Pro adds the in-admin Build with AI panel for people who would rather not connect an external client.
No. It goes through the builder's own validation, and reconfiguring a form never touches the responses already collected.
Any MCP client that can authenticate to your site. The documented walkthrough uses Claude because that is what most people ask about first.
The five-question intake form nobody wants to sit down and write is exactly what this is good at. Install the free plugin and point your assistant at your site.
Download free Read the setup guide