Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
mcpb https://github.com/WatermelonBros/reado/releases/download/v1.34.0/reado.mcpbO Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add io.github.watermelonbros-reado -- mcpb https://github.com/WatermelonBros/reado/releases/download/v1.34.0/reado.mcpbExecute em um terminal.
{ "mcpServers": { "io.github.watermelonbros-reado": { "command": "mcpb", "args": [ "https://github.com/WatermelonBros/reado/releases/download/v1.34.0/reado.mcpb" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Your agent writes more code than you do now. The job that's left is reading it and deciding — and that deserves a tool of its own. In Reado you read, and you leave comments anchored to the exact lines that matter; your agent (Claude Code, Codex, Copilot, Gemini, OpenCode or Cursor) resolves them, and you review what changed.
Inverted code review: you are the reviewer, the AI is the committer.
Your code review comments from Reado, the read-first IDE, as context and tools for your agent.
Pick what to review — your working changes, a branch, a pull request — and a focus: bug risk, security, performance, test coverage. The agent plans a route through the change, reviews it file by file and proposes; nothing is final until you approve it.
A Reado comment is not a sticky note. It is anchored to a line range, typed
(bug, refactor, performance, question, note), threaded, and either a task for
the agent or a note for the next reader. Comments live next to your code as
plain Markdown in .reado/, and they survive edits: when the code moves, they
re-anchor with it — and one whose code is gone becomes an orphan instead of
quietly pointing at the wrong line.
Send review hands your open tasks to the agent running in Reado's terminal.
It works through the reado CLI and MCP server — reading your comments, consulting
the project's docs and specs, resolving each task — and Reado reflects every step
live: the reasoning, the files it touches, the task closing. When it's done, a
Δ on the file tree takes you straight to what changed since you last read it.
tour.json with your repository and anyone who opens it
in Reado can walk the code you'd explain to a newcomer, the exact lines lit up and
explained step by step. The format is open — any tool can
read and write it.Reado is MIT and runs on macOS, Linux and Windows. Your code and your comments stay on your machine as plain files; an account is optional and never gates the app.
Grab the latest signed build from
Releases — macOS
(.dmg, signed & notarized), Linux (.AppImage / .deb / .rpm) and Windows
(.exe / .msi). Reado updates itself from signed releases after that.
Reado's core loop is read → annotate → AI-resolve:
Cmd/Ctrl+J), launch Claude, Codex or Copilot,
then click Send review. Reado injects a prompt pointing the agent at your
open tasks.reado://tasks and
reado://comments MCP resources, or reado task list — makes the changes,
and marks each done with reado task done <id> (or reado task fail <id> "<reason>"). Reado's watcher reflects the result live, and resolved comments
move to history.The reado binary is the stable contract — the on-disk format can evolve without
breaking the agents. It serves both the MCP server (reado mcp, auto-wired
into each agent's config on project open) and the CLI the agent calls, so it
must be on the agent's PATH for the AI loop to work. The packaged app bundles
it: install from Settings → Command-line tool (links reado into
~/.local/bin, VS Code style). The MCP server is also listed in the
official MCP Registry
as io.github.WatermelonBros/reado, as a bundle with the binary for macOS, Linux and
Windows. From a source checkout, build and link it
directly:
scripts/install-cli.sh # builds release + links into ~/.local/bin
reado --help
Actions (CLI): reado task list|show|done|fail|link,
reado comment add|reply|search, and reado kb list|show|search (to consult
the docs and specs before resolving). Context (MCP): the reado://tasks,
reado://comments, reado://reading-progress and reado://bookmarks resources,
plus browser_* tools for the in-app preview. Agent identity comes from
$READO_AGENT (Reado sets it when launching an agent).
An agent plugin in plugin/ teaches Claude Code (and Codex, via
AGENTS.md) this contract so the agent resolves tasks correctly. See
plugin/README.md to install it. Other agents (e.g. Copilot)
still get the contract from the Send review prompt Reado injects, as long as
the reado CLI is installed.
Reado aims to be a friendly open-source project, and contributions are welcome. Everything you need to build, test and send a change — prerequisites, the dev loop, the checks CI runs, conventions — is in CONTRIBUTING.md. Please read our Code of Conduct; security issues go through SECURITY.md.
MIT © Reado contributors
Your code review comments from Reado, the read-first IDE, as context and tools for your agent.
{ "mcpServers": { "io.github.watermelonbros-reado": { "command": "mcpb", "args": [ "https://github.com/WatermelonBros/reado/releases/download/v1.34.0/reado.mcpb" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Reado roda localmente via stdio.
Última verificação: 2026-11-09. Your code review comments from Reado, the read-first IDE, as context and tools for your agent.