The Model Context Protocol (MCP) is an open standard that lets an AI assistant, such as ChatGPT, Claude or an AI coding tool, call tools on another system. PageForge includes an MCP server, so an assistant you connect can look at your PageForge site and answer questions like “which generated pages are missing a meta description?” using real data instead of guesses.
It is off by default
Nothing is reachable until an administrator turns it on:
- Go to PageForge > Connections.
- Under MCP / AI Clients, tick the enable checkbox. The badge changes from Disabled to Enabled.
- Note the Endpoint. It is your site address followed by
/wp-json/pageforge/v1/mcp.
https://example.com/wp-json/pageforge/v1/mcp
Turning it off again refuses every request immediately, including new sign-ins.
Free and Pro
| PageForge Free | PageForge Pro | |
|---|---|---|
| Read templates, pages, SEO status and diagnostics | Yes | Yes |
| Check rows and preview pages before generating | Yes | Yes |
| Create campaigns, update SEO metadata, fix image ALT text | No | Yes, with scopes an administrator approves |
| Preview and confirmation before changes | Not needed, nothing is written | Required for risky changes |
| Log of changes made through MCP | Not needed | Yes |
PageForge Free registers no tool that can change your site. An assistant connected to Free can read, check and preview, and that is all.
What an assistant can do in Free
| Group | Tools |
|---|---|
| Site and setup | PageForge site status, PageForge diagnostics, List available post types, List taxonomies and terms |
| Templates and pages | List PageForge templates, List generated PageForge pages, Read one page or post, Search site content |
| Before generating | Preview PageForge variable resolution, Preview a generated page, Validate rows before generation, Check builder compatibility |
| SEO | Read SEO metadata for one page, Audit SEO across content, SEO integration status, Find images missing ALT text, Preview improved SEO metadata |
Everything an assistant sees is limited by the permissions of the WordPress user who approved the connection.
Ways to connect
| Client | How it signs in | Button on the Connections screen |
|---|---|---|
| ChatGPT | OAuth, you approve in WordPress | Set up ChatGPT |
| Claude (web and desktop apps) | OAuth, you approve in WordPress | Set up Claude |
| Cursor, VS Code, GitHub Copilot, Claude Code, Codex, Roo Code and other clients | Personal access token in a request header | Create personal access token |
Prompts to try
Show my PageForge site status.
List my PageForge templates and the placeholders each one uses.
Validate these five rows against the "Plumbing in City" template before I generate.
Audit SEO on my generated pages and list the ones missing a meta description.
Note The AI provider key in Settings and an MCP connection are separate. The key lets PageForge call an AI. An MCP connection lets an AI call PageForge.
Next: Connect ChatGPT and Scopes, permissions and security.
