The problem: an agent cannot see what you are pointing at
An AI coding agent will change a website as fast as you can describe the change. The describing is the slow part. “Make the heading on the pricing card smaller” leaves the agent to search the repository for which heading, on which card, in which template. A pasted screenshot helps a person; it gives an agent pixels, not a selector.
What an agent needs is what a developer needs, written down: the page, the element, its HTML, and what the person wants. That is what a ClickNote note is.
How feedback reaches the agent
- Someone leaves notes on the site. A client, a product manager or you: open the review link, click the element, write what should change. Each note is saved with its page, CSS selector, XPath, the element’s text and HTML, the device and a screenshot.
- Connect the agent, once. ClickNote has an MCP endpoint on every plan, at
https://app.clicknote.io/mcp. Claude and ChatGPT connect by signing in: you give them the address and say on ClickNote’s own page how much they may do. Claude Code, Codex and Cursor connect with an API key that an owner or admin makes in the dashboard. - Ask in plain words. “List the open notes on this project.” “Read note 3 and find the file that headline comes from.” “Fix the copy notes on the home page, set each one to done and add an internal note saying what you changed.”
- Review the change as you would any other. The person who left the note sees its status change on the site.
For Claude Code the connection is one command, with your key in place of the placeholder:
claude mcp add --transport http clicknote https://app.clicknote.io/mcp \
--header "Authorization: Bearer <key>"What the agent is given
Reading one note in full gives the agent the page, the platform and theme, the section, block or builder container the element sits in, the selector and XPath, the element’s text and HTML, its attributes and styles, the device, the reviewer’s words, the thread of replies, your internal note, and a signed link to the screenshot that works for 24 hours. With the selector and the HTML an agent can usually find the element in the code without opening the picture.
At the lowest level, Notes only, an agent has 5 tools: list_projects, list_comments, get_comment, update_status, add_internal_note. It can read projects and notes, set a note to open, in progress or done, and add to a note’s internal note. That is all a coding agent needs to work through feedback.
You choose how much it may do
Every key and every connected app has one of 3 levels, and nothing gets more than a person chose. Notes only is the level already chosen when a key is made. Notes and projects lets an agent also set up projects, invite reviewers and reply to clients in a note’s thread; tools that send email say so, and ClickNote tells the agent to ask you first. The highest level adds brands, workspace settings and the team.
Some things no agent can do at any level: change how anyone signs in, make or revoke a key, touch billing or the plan, delete a project, or leave, edit or delete a client’s note. An app that signed in works as you and can never do more than you can in the dashboard. Disconnect or Revoke stops an agent at once. The levels and every tool are in the docs.
Without connecting anything
Every note in the dashboard has a Copy for AI agent button, and Copy all for AI agent sits above the list for the notes you have filtered. Each puts the same context on your clipboard as a Markdown brief: the page, the selector, the element’s text and HTML, the device, and the reviewer’s comment. Paste it into any assistant, or into a ticket for a person.
Developers and product managers
A developer working with Claude Code, Codex or Cursor in the site’s repository connects with a key and lets the agent go from a note to the change, then to the note’s status.
A product manager who does not open the repository can still brief an agent well: leave the notes on the site, then hand them over with Copy for AI agent, or connect Claude or ChatGPT by signing in and ask what is open on a project. See feedback from product managers to developers.
What ClickNote does not do
- It does not write or change code, and it has no access to your repository. Your agent does the work.
- An agent cannot leave notes on a site. It has no reviewer access. Notes come from people.
- It does not read your conversation with the assistant. It receives only the calls the assistant makes to its tools.
- It does not check the fix. Setting a note to done is the agent’s claim; a person looks at the page.
- Notes are about web pages. Not server code, APIs or native apps.