Detected automatically once HappyForms is active.
HappyForms allows a form that neither emails anyone nor keeps what was submitted — so every form is checked for exactly that.
Read and build forms with the parts HappyForms uses.
Read and update the settings behind each form.
Read what people sent you.
Flags a form that neither emails nor stores, before an enquiry vanishes.
Detected automatically once HappyForms is active.
Permanent deletion asks for confirmation first.
Ask in plain language and the HappyForms integration turns it into typed calls — no exports, no SQL, no brittle scripts.
Apply a change across every form at once.
Have an assistant draft a working form from a description.
Find forms that collect submissions without telling anyone.
Chain HappyForms steps into longer workflows.
The NibWP HappyForms integration connects any MCP-compatible AI agent — Claude, Cursor, Claude Code and others — to your forms through typed, schema-validated tool calls. HappyForms allows a form that neither emails anyone nor keeps what was submitted — so every form is checked for exactly that.
| Tool | Type | What it does |
|---|---|---|
| nibwp/happyforms-forms | write | List, create and duplicate forms. |
| nibwp/happyforms-parts | read | Read the parts that make up a form. |
| nibwp/happyforms-settings | read | Read form settings. |
| nibwp/happyforms-submissions | read | Read stored submissions. |
| nibwp/happyforms-audit | read | Check a form emails or stores what it receives. |
Yes — once HappyForms is installed, NibWP detects it and its abilities go live.
Yes. It creates and updates as well as reads, and anything permanent asks for confirmation first.
Yes — the audit checks whether submissions are actually stored and whether anyone is notified.
No — the HappyForms integration is part of Pro. Pro Skills are for design-to-build builder output.
Activate the integration and it's live on your MCP endpoint instantly.