What works
Cursor connects to PageForge as an MCP server over HTTP and authenticates with a personal access token. The token travels in the X-PageForge-MCP-API-Key header, never in the URL, and it carries only the scopes you chose when you created it.
With PageForge Free, Cursor’s agent can read templates, generated pages, SEO fields and diagnostics, check rows against a template, and preview pages without creating them. That is useful when you build a theme or a page template in Cursor and want the agent to see the placeholders and data it has to work with.
With PageForge Pro, the agent can also make changes you approve, such as updating SEO titles and descriptions or starting a generation run. Bulk and risky changes are previewed first and run only after you confirm.
Set it up
- In PageForge > Connections, turn on the MCP connection.
- Under other MCP clients, choose Create personal access token, give it a label and pick its scopes.
- Copy the token. PageForge stores only a hash and cannot show it again.
- Choose the Cursor option under Client configuration, click Copy configuration and paste it into
.cursor/mcp.json. - Restart or reload Cursor’s MCP servers and check that PageForge appears.
Limits and notes
- MCP support and settings belong to Cursor and can change between versions or plans. Check Cursor’s documentation if the file format differs.
- Keep
.cursor/mcp.jsonout of version control once it holds a token. - Tokens do not expire on their own. Revoke a token in Connections when you no longer need it.
Pro Approved changes are available on every Pro plan with an active license.
