In PageForge Pro, an AI assistant can do more than read. It can generate pages from a template, update SEO metadata and fix missing image ALT text. Each of these is a separate tool, each needs a scope you approve, and the risky ones always show a preview before anything changes.
Pro Write tools are included in every PageForge Pro plan (Starter, Professional and Enterprise) while the license is active. Without an active license, MCP stays read and preview only.
Turn it on
- Go to PageForge > Connections and tick Enable PageForge MCP. On a licensed site the label next to it reads Full MCP · Operate PageForge.
- Grant scopes to each connection:
- ChatGPT and Claude: the Authorize AI client access screen lists the permissions requested. Approve only if they fit what you want the assistant to do.
- Other clients: before Create personal access token, choose the boxes under Access this token may use. On a licensed site the operating scopes are ticked by default, so untick any the client does not need.
Administer PageForge is never part of a default grant.
What assistants can change
| Tool | Scope needed | Confirmation |
|---|---|---|
| Create a campaign: generate pages from a template and up to 500 rows, as draft, pending, private or published | Create and update content | Required for more than one row, or when the rows fail validation |
| Cancel a campaign and remove its remaining queue items | Operate campaigns | Always |
| List campaigns and their progress (read only) | Operate campaigns | Not needed |
| Update SEO metadata for one page: SEO title, meta description, focus keyword | Manage SEO | Always |
| Bulk optimize SEO metadata for up to 500 posts | Manage SEO | Always, never writes on the first call |
| Set image ALT text on one image | Manage SEO | Always |
| Bulk update image ALT text, up to 100 fixes | Manage SEO | Always |
SEO changes are written through your active SEO plugin, the same way as in the admin screens. Every call still runs as the WordPress user behind the connection, so the assistant cannot edit or publish anything that user could not.
Preview, then confirm
When a tool needs confirmation, the first call changes nothing. PageForge returns a preview of exactly what would change and a one-time confirmation code. The change happens only when the assistant calls the tool again with identical details and that code.
- The code works once and expires after five minutes.
- It is tied to the exact arguments and the connection that asked for it. Change one value and a new preview is required.
A typical exchange:
You: Fix the meta descriptions on my 12 Austin plumbing pages.
Assistant: Calls "Bulk optimize SEO metadata". PageForge returns proposed
titles and descriptions for 12 pages, plus a confirmation code.
Assistant: Shows you the proposals and asks whether to apply them.
You: Apply them, but skip the drain cleaning page.
Assistant: Changing the list needs a new preview, so it calls the tool
again without that page and shows you the result to confirm.
Tip Tell your assistant to always show you PageForge’s preview and wait for your go-ahead before confirming. Whether it pauses to ask you depends on the assistant, not on PageForge.
Activity log
Every write attempt, successful or not, is recorded and listed under MCP activity on the Connections screen. Each entry shows the tool, the result, the time, whether it was a preview or an execution, the risk level and the client. The record also keeps the scope, the affected post IDs and whether a confirmation was used.
The log never stores secrets, raw tokens, full prompts or page content. Values that look like credentials are removed, including inside nested data. The most recent 1000 entries are kept.
Next: Scopes, permissions and security and Connect ChatGPT, Claude and other AI assistants.
