PageProofer

What the PageProofer MCP server does

The PageProofer MCP server gives coding agents access to website feedback collected in PageProofer. A client or teammate can click an element on a website, leave a note, and provide the agent with contextual data such as the page URL, selected element, browser details, console errors, and failed network requests.

The agent can use that information to investigate the corresponding code, make a fix in the project, explain the change in a note comment, and send the note to in review. A person remains responsible for checking the result because agents cannot mark notes complete or closed.

How it works

PageProofer exposes a hosted MCP endpoint at https://app.pageproofer.com/mcp using streamable HTTP. Requests are authenticated with a bearer token. The repository documents the service; the MCP server itself runs as part of PageProofer, so no local server package needs to be installed.

A typical workflow starts by listing available sites and their open note counts. The agent then filters or reads notes, retrieves relevant screenshots or attachments, and uses the captured page and element details to locate the issue in the project. After making a code change, it can add a comment—optionally including a commit reference—and update the note to in review.

The agent operates with the same site and note visibility as the authenticated user. Comments are attributed to that user and marked as sent via an AI agent. Feedback text and comments are treated as problem descriptions rather than instructions to the agent.

Setup and configuration

Create a token in PageProofer by opening My Settings, selecting AI agents, naming the token, and choosing Create token. The token is shown only once. Store it as a secret and revoke it from the same settings area if it may have been exposed.

For VS Code with GitHub Copilot, configure an HTTP MCP server in .vscode/mcp.json or the user MCP configuration. VS Code can prompt for and securely store the token. Claude Code can be configured with its HTTP transport command, while Cursor uses ~/.cursor/mcp.json or a project-level .cursor/mcp.json with the endpoint and Authorization header.

Other MCP clients can connect if they support remote servers over HTTP. The PageProofer MCP server does not require an environment variable; authentication is supplied through the request header.

Tools and capabilities

• list-sites shows accessible websites, domains, open note totals, and site members.
• list-notes returns notes newest first and can filter by status, tags, text, page, assignee, or overdue state. It shows open notes by default.
• get-note returns the note content, page URL, pinned element details, browser and viewport information, console errors, failed requests, comments, and attachments.
• get-attachment retrieves screenshots and other attachments. Images are supplied as viewable images, while text files are returned as content.
• add-comment posts a comment as the authenticated user and supports internal team-only comments.
• update-note changes a note's status, priority, assignee, or due date.

Limitations and notes

The PageProofer MCP server cannot close or complete notes. Its workflow ends by moving a fixed note to in review for human verification. Access is limited to sites and notes visible to the token's user, and all agent activity uses that user's identity.

Keep the bearer token out of source control and do not share it as ordinary configuration. AI agent access is available on PageProofer plans, including the free trial, and tokens can be created per computer or tool and revoked later.