What works
VS Code can talk to MCP servers listed in a workspace’s .vscode/mcp.json file. PageForge gives you that entry ready to paste: an HTTP server with your site’s MCP URL and a personal access token in the X-PageForge-MCP-API-Key header. Agent features in VS Code, such as GitHub Copilot’s agent mode, can then call PageForge tools.
With PageForge Free, the connection is read-only: templates, generated pages, SEO fields, diagnostics, checks of rows against a template, and previews of pages that do not exist yet. With PageForge Pro, the agent can also make changes you approve, such as SEO updates, ALT text fixes and generation runs. Bulk and risky changes are previewed and need your confirmation.
Set it up
- In PageForge > Connections, turn on the MCP connection.
- Choose Create personal access token, give it a label and select its scopes.
- Copy the token now. PageForge keeps only a hash of it.
- Under Client configuration, choose VS Code / GitHub Copilot, copy the configuration and paste it into
.vscode/mcp.jsonin your workspace. - Start the server from VS Code’s MCP controls and confirm PageForge’s tools are listed.
Limits and notes
- MCP support depends on your VS Code version and on the extension or plan you use with it. Follow VS Code’s MCP documentation if its settings change.
.vscode/mcp.jsonis often committed with a project. Do not commit the token. VS Code can prompt for secret values instead of storing them in the file.- Tokens do not expire on their own. Revoke them in Connections when a project ends.
Pro Approved changes are available on every Pro plan with an active license.
