PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

AI assistants · MCP

Let ChatGPT and Claude read your campaigns, safely

PageForge includes a Model Context Protocol server. Connect the assistant you already use and ask it which pages are missing descriptions, why a run would skip rows, or what a template change would do, without giving it the keys to your site.

An AI assistant connected to PageForge reads generated pages and previews changes without saving anything.

What an assistant can do

Read and preview on Free. Approved changes on Pro.

Free · read, check, preview

  • Site and plugin status, diagnostics and builder compatibility
  • Templates, variables and generated pages
  • SEO, meta and schema status for generated pages
  • The pre-generation check: unmatched placeholders, duplicate URLs, missing data
  • Previews of titles, URLs, content, SEO fields and schema, with nothing saved
  • No write tools are registered at all

Pro · changes you approve

  • Everything on Free
  • Write tools an administrator switches on, scope by scope
  • Preview first, then apply
  • An audit log of assistant actions, with credentials redacted
  • Image alt-text audits with confirmed updates

Security

An assistant gets exactly the access you give it

Off by default

Nothing is reachable until an administrator enables the connector.

Acts as a WordPress user

Each connection is consented to by a user and limited by that user’s role and the scopes granted.

Tokens you control

Personal access tokens are stored only as hashes, can be rotated or revoked individually, and travel in a header, never in a URL.

OAuth with PKCE

ChatGPT and Claude connect through OAuth with PKCE, resource indicators and token revocation.

Checked on every object

Requests that touch content are checked against WordPress capabilities post by post, and rate limited.

Diagnostics built in

The Connections screen tests HTTPS, REST access, header forwarding and OAuth metadata, and lists rejected requests.

Setup

Connected in three steps

  1. Enable the connector. In PageForge, open Connections and switch it on. Copy your server URL.
  2. Add it to your assistant. In ChatGPT or Claude, add a custom connector with that URL and approve the consent screen. In Cursor, VS Code or Claude Code, create a personal access token and add it as a header.
  3. Ask. “Which generated pages have no meta description?” “Preview what this template change would do to the Dallas pages.”

Questions

About AI access

Is this the same as the AI key in PageForge settings?

No. The AI key lets PageForge call a provider for planning and drafts. The assistant connection lets an assistant you chat with call PageForge. They are separate and you can use either, both or neither.

Does the assistant get admin access to WordPress?

No. It works through PageForge’s own tools only, as the WordPress user who approved the connection, within the scopes granted. On Free there are no write tools.

Which ChatGPT or Claude plan do I need?

That depends on OpenAI and Anthropic, and they change it from time to time. Check whether your plan allows custom connectors; coding tools like Cursor and Claude Code use a token instead.

How do I cut off access?

Revoke the grant or token on the Connections screen, or switch the connector off. Access stops immediately.

Build the template once. Let the data do the rest.

Install PageForge from WordPress.org, upload a five-row CSV and preview your first page in a few minutes. Upgrade only when you need the automation.

↑↓ to move↵ to open