Your coding agent reads the review.
Every board is also an MCP server. The agent in your editor gets each comment with the element it points at and answers in the thread.
- Work through the open notes on the admissions board
- pagecomment_list_annotations({ status: "open" })
- 3 open: inspect on a.apply-cta, a selection, a comment
- pagecomment_suggest_edit({ text: "Apply by Jan 15", suggestion: "Apply by March 1", answering: "q81m" })
- Suggestion posted on the highlighted text
- pagecomment_resolve({ id: "k3f9", summary: "Raised the Apply button to 4.8:1 contrast" })
- Resolved. The summary is now a reply in the thread
- Claude CodeRaise the contrast on the Apply button
- CursorThe hero image crops her face on a phone
- CodexThe deadline moved to March 1
- VS CodeFooter links overlap at 375px
- Claude CodeUse the new logo in the nav
- CursorThis table needs a caption for screen readers
- CodexTypo in the second paragraph: recieve
- VS CodeDefault the pricing switch to yearly
How an agent fits in. It works the board the way a teammate would.
Replies in the thread
A question goes under the note it is about, signed with the agent’s name, so the reviewer answers where they left it.
pagecomment_reply
Suggests the edit
For copy, it proposes the exact replacement. The board shows the old words struck through above the new ones.
pagecomment_suggest_edit
Resolves with a reason
Closing a request posts a summary of what changed. When it cannot act, it dismisses with a reason the requester sees.
pagecomment_resolvepagecomment_dismiss
A person decides what ships. The agent changes code where you run it, so its edits go through your review like anyone else’s.
Watch it work. Progress shows on the board as it happens.
pagecomment_watch_annotations waits for new notes and hands them over as a batch, so an agent calling it in a loop picks up feedback while the review is still going.
Before it changes anything, pagecomment_acknowledge marks the note in progress. Its replies and status changes reach everyone with the board open, live.
- AnaOpenThe Apply button is hard to read on the blue
- Claude CodeIn progressPicked up
- Claude CodeResolvedDarkened the button fill in Apply.tsx, now 4.8:1
Connect a client. One line, nothing to install.
A board answers MCP at its own link plus /mcp. A project link reaches every page in it, and each annotation says which page it is on.
claude mcp add --transport http pagecomment https://pagecomment.com/board/abc123/mcpAdd ?agent=Your%20Name to the address to sign the agent’s replies. A board kept to a team also takes a team agent key, sent as Authorization: Bearer pck_….
Prompts to start with. Paste one once the board is connected.
Work through the open PageComment notes. Acknowledge each one before you change anything, and resolve it with a one-line summary.
List the open annotations and group them by component before you touch any code.
For copy changes, use pagecomment_suggest_edit and leave the request open for me to review.
Watch the board while I review. Pick up each new note as it arrives, and reply if anything is unclear.
Why a board beats a screenshot. The agent gets what the reviewer pointed at.
| Capability | PageComment over MCP | A pasted screenshot | Comments copied into chat |
|---|---|---|---|
| Sees the exact element | Yes | No | No |
| Gets the selector and markup | Yes | No | No |
| Reads the whole thread | Yes | No | What you paste |
| Can resolve the request | Yes | No | No |
| Picks up new notes as they arrive | Yes | No | No |
Build your own. Run an agent that answers requests on its own.
Agent API
A team webhook posts each new comment, reply and status change, signed with HMAC-SHA256. The agent reads the board, replies and sets the status over REST at /api/agent, with a key a team admin creates.
The whole team
A team answers MCP at /team/your-team/mcp. With a team agent key, the agent reaches every board the team holds and watches them all for new requests.