Send review feedback to your coding agent, with MCP

Your team has reviewed the app and left twenty or so comments. Now they need fixing. With a coding agent that goes fast, as long as you explain each piece of feedback: copy the comment, describe the screen, find the component it is about. Twenty times.

That copy-pasting is exactly what MCP lets you skip.

MCP, in two sentences

MCP (Model Context Protocol) is a standard that lets a coding agent, like Claude Code or Cursor, use outside tools: read data, call actions. An “MCP server” exposes those tools, and the agent calls them when it needs them.

Riqoch MCP is the MCP server of Riqoch. It is included in the desktop app and gives your agent access to the review feedback left on your app.

Why it helps

A comment left in Riqoch isn’t a note on a screenshot: it is attached to an element of the real app, built from your code. When your agent reads that comment, it knows which element it is about, which helps it find where to make the change.

And you no longer have to rephrase anything: you give the agent the comment’s link, and it reads it itself.

Setting it up

1. Turn on Riqoch MCP in the settings of the Riqoch desktop app.

2. Add it to your agent. The server is served by the app, at http://127.0.0.1:51747/mcp, over HTTP.

With Claude Code, in a terminal:

claude mcp add --transport http riqoch http://127.0.0.1:51747/mcp

With Cursor, in .cursor/mcp.json:

{
  "mcpServers": {
    "riqoch": { "url": "http://127.0.0.1:51747/mcp" }
  }
}

With another agent, in its MCP configuration:

{
  "mcpServers": {
    "riqoch": { "type": "http", "url": "http://127.0.0.1:51747/mcp" }
  }
}

You can also copy the setup prompt from the download page and give it to your agent: it adds the server itself.

3. Check that it answers. Ask your agent to call list_files with the folder you are working in: it should find your Riqoch file.

Day to day

Once it is set up, the loop looks like this:

1. You publish a version of your app as a review link, and your team or your client comments on it.
2. You copy a comment’s link (app.riqoch.com/projets/…) and give it to your agent.
3. The agent reads it with get_thread, or reads all of a file’s comments with list_threads.
4. It makes the change in the code, then reports it with report_change.
5. You check, publish again: the same review link shows the new version.

You stay in charge

One important point: the agent never resolves a comment thread. You do, once you have checked the fix. The setup prompt Riqoch provides tells the agent so explicitly. A piece of feedback is only closed when a human has decided it.

In short

Riqoch MCP connects both ends of the loop: the feedback your team leaves on the real app, and the agent that writes the code. Less copy-pasting, feedback that arrives with its context, and the final call that stays yours.

Download Riqoch to try it with your agent.