mdr_request_reviewLABSCO SUMMARY
Spec review that works like code review.
The comments are anchored to the text and stored in the file, so feedback arrives as a structured prompt rather than a paragraph of "in the third section, change…" — and because the agent can request a review and block, the checkpoint happens before it builds on the wrong version.
What it is
A local review tool for specs, prompts and design docs. You highlight text in a rendered view and leave comments; they are stored as invisible HTML markers inside the .md file itself, so there is no sidecar file, no database and no service — the markdown stays the source of truth. With the MCP server registered, review works in both directions: the agent can pause and ask for yours, or leave anchored comments on a doc you wrote.
What you get
mdr_request_review— the agent pauses mid-task, mdr opens the file, and it waits while you highlight and comment; Send N comments delivers a batch, Send N & finish closes the loopmdr_review— the agent reviews your document and leaves its findings as inline comments anchored to the exact text, with the browser opening so you read them as they arrivemdr_ask— anchored questions posted into the doc at a fork the agent cannot resolve alone, blocking until you answermdr_wait— how the agent holds the session while a review is in progress- The viewer and commenting themselves, from
npx md-redline /path/to/spec.md— no MCP required for that half
Requirements
Node 20 or newer. npx md-redline /path/to/spec.md starts the local app and opens it; installing globally gives you mdr for a file, a directory, or mdr --stop. Register the MCP server with mdr mcp install for Claude Code and Claude Desktop, codex mcp add md-redline -- mdr mcp, or gemini mcp add --scope user md-redline mdr mcp — the --scope user flag matters, because Gemini otherwise registers it for the current directory only. For any other client, mdr must be on the PATH of the process your client spawns; use the absolute path from which mdr when it is not. Update checks run once a day and can be turned off with NO_UPDATE_NOTIFIER=1, which is a presence check, so any value disables it.
Setup effort
One command — npm install -g md-redline
USE CASES
01
Marking up a spec the agent just drafted
Tell it to let you review first — it pauses, you highlight and comment, and it starts addressing your feedback when you send the batch.
02
Getting a critique of a document you wrote
Point the agent at your PRD; its findings land as inline comments anchored to the exact lines rather than as a wall of text.
03
Answering the question that would otherwise be guessed
At a fork, the agent posts an anchored question into the doc and waits for your answer instead of picking a direction.
04
Reviewing a spec from another repo
Open any markdown file in the viewer and comment on it — the comments travel with the file, since they are in it.
05
Iterating without losing your place
Keep sending follow-up batches while the agent works, and close with the final send when the document is where you want it.
4 tools
Listed in project docs. Your client may show a different list.
mdr_reviewmdr_askmdr_waitBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
mdr on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g md-redlineMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
mdr mcp install --claude-codeClaude Desktop
CLAUDE DESKTOP · TERMINAL
mdr mcp install --claude-desktopCodex
CODEX · TERMINAL
codex mcp add md-redline -- mdr mcpGemini CLI
GEMINI CLI · TERMINAL
gemini mcp add --scope user md-redline mdr mcpAny MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"md-redline": {
"command": "mdr",
"args": [
"mcp"
]
}
}
}
