FormForge Pro Operations

Prerequisites

• FormForge Pro installed and active (see the plugin page at royalplugins.com/formforge)
• Royal MCP Pro installed and licensed (see Getting Started)
• MCP client connected to your site (Claude Desktop, ChatGPT connector, Cursor, or any MCP-compatible client)
• Your MCP-connecting WordPress user needs manage_options for form CRUD and bulk operations, or edit_posts for entry reads (see capability model)

Tools that reference a form or entry by ID refuse when the target can't be resolved and return form_not_found or entry_not_found. Nothing is partially written on a resolution failure.

Capability model

FormForge Pro Operations tools use two capability tiers matching the two kinds of work they do:

• edit_posts — entry reads (formforge_get_entry, formforge_get_analytics) and paginated bulk export. Reading entries is a content-editor-scoped operation, not a site-admin one.
• manage_options — bulk delete, bulk resend notifications, duplicate form, create from template. Anything that changes site-wide form configuration or dispatches emails requires administrator.

Every tool falls back to manage_options if the scoped capability is missing. If your MCP-connecting user is an administrator this is all transparent.

Shared safety layer

Every FormForge Pro write tool runs through the same safety layer used across Royal MCP Pro's write surface, with a couple of FormForge-specific patterns:

• Cap checks. Every tool checks the appropriate scoped cap first (edit_posts for reads, manage_options for writes and email dispatches). Fails-first with insufficient_caps if the caller doesn't have it — no partial writes.
• Form + entry resolution. Tools that reference a form or entry by ID resolve against FormForge's own registry first and refuse with form_not_found / entry_not_found if the target doesn't exist. No silent creation.
• Confirm tokens on bulk delete. formforge_bulk_delete_entries is two-step by design: call once with the entry ID set to get a five-minute confirm token plus a preview count; call again with the token to persist. Prevents accidental fat-finger deletes.
• 72-hour undo tokens on destructive writes. formforge_bulk_delete_entries and formforge_duplicate (undo-able direction) return an undo token good for 72 hours. Undo on delete restores every deleted entry with its exact prior payload; undo on duplicate deletes the created form.
• No undo on email dispatches. formforge_bulk_resend_notifications returns undo_token: "NO_UNDO_SCOPE" — emails already left the box. Preview machinery on the read step lets you eyeball the recipient set before firing.
• Audit Log row on every call. Success, error, and undone states all produce audit rows.

The 7 tools

Grouped by write shape. Two read tools (entry data + analytics) require the edit_posts capability; three bulk operations and two form-creation tools require manage_options.

Entry reads (2)

Side-effect-free. edit_posts capability required.

Show me the full details of FormForge entry 4287, including any UTM parameters captured on submission.

Show me the analytics for form 12 over the last 14 days, including field-level completion rates.

Bulk operations (3)

Bulk export is read-only. Bulk delete is a two-step confirm flow with a 72-hour undo. Bulk resend notifications dispatches emails — no undo scope.

Export the last 30 days of completed submissions from form 12, 200 per page, ordered by submission date descending.

Delete FormForge entries 4200 through 4285 (the test submissions I made while setting up the form).

Re-fire the admin notification email for entries 4287 through 4295 (they were submitted while my SMTP provider was down).

Form creation shortcuts (2)

Both tools create a new FormForge form. Duplicate copies an existing form (including notification config, field logic, and styling); create-from-template spins up a new form from a FormForge Pro template.

Duplicate form 12 ("Contact Us") as "Contact Us — Landing Page Version" with notifications and confirmations copied.

Create a new form titled "2026 Customer Feedback" from the "customer-satisfaction-survey" template, sending notifications to feedback@example.com.

Related reading

• Undo Tokens & Reversibility — how the 72-hour undo tokens returned by formforge_bulk_delete_entries and formforge_duplicate work, when they expire, and how to consume them via royal_mcp_undo_last_operation.
• Universal Audit Log — every FormForge tool call is captured, including bulk delete confirms and undo dispatch.
• FormForge Pro plugin — the underlying form builder these tools wrap.
• FormForge Pro support — documentation for the form builder itself (form CRUD, notification rules, field logic, conditional display).

Still Stuck? Two-Step Support Path

If a FormForge Pro tool isn't behaving the way you expected, work through these two steps in order — most tool-level failures resolve at Step 1 because they're actually MCP-connection, host-layer, or FormForge-Pro-availability issues, not FormForge Pro Operations specific.

Step 1: Start with the Royal MCP Troubleshooting Guide

Royal MCP Troubleshooting — Start Here covers MCP-layer issues. If Claude can't reach your site at all, the tool call never fires — that guide is where to start.

For Pro-specific patterns:

• Undo token errors — expired, consumed, or handler missing
• Undo Tokens & Reversibility — how the 72h undo flow on destructive tools works
• Pro tool returned upgrade prompt with valid license

For FormForge Pro-specific patterns:

• formforge_pro_not_active. Every tool on this page requires FormForge Pro. The free FormForge plugin doesn't include the analytics API, template system, or bulk-notification hooks these tools wrap. Install FormForge Pro from royalplugins.com/formforge to unlock.
• form_not_found / entry_not_found. The tool couldn't resolve the target by ID. Confirm the form or entry ID via the FormForge admin (WP Admin → FormForge → Forms or → Entries) before re-calling.
• confirm_token_invalid on formforge_bulk_delete_entries. Confirm tokens are one-shot with a 5-minute TTL. If the token expired or was already consumed, re-run step 1 with the entry ID list to get a fresh token.
• batch_too_large. Every bulk tool caps at 500 entries per call. Narrow the filter or split the batch and re-call.
• Notifications not firing on formforge_bulk_resend_notifications. The tool wraps FormForge Pro's own send_notifications() path, so if notifications aren't firing when you re-fire them here, the underlying cause is the same as when they don't fire on original submission — usually SMTP config. Check WP Admin → FormForge → Settings → Email Log, then Royal SMTP (or your SMTP plugin) admin dashboard.

Step 2: Email priority support

If you've worked through Start Here and the relevant Pro-specific doc and the issue still isn't resolved, email priority support from your purchase email address at support@royalplugins.com. Priority email support is included with your license — typical response within 24 hours. Never include your license key in email; we look it up from your purchase address.