SkillTide Submit
Official description3 sourcesMCP servers3d ago
plannotator

plannotator

Interactive plan review UI with visual annotation (install via /plugin marketplace add…
View on GitHub ↗Direct link · no redirect page
Official descriptionInteractive plan review UI with visual annotation (install via /plugin marketplace add backnotprop/plannotator)
Source
collected from the ccplugins/awesome-claude-code-plugins list · type: MCP server
Harvest history
first seen 2026-10-14 · last seen 2026-10-16 · seen 4× · listed by 3 sources
Score
score 303 · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-14;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals

Everything you need to annotate and stay in the loop with your agents

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Markdown Review • Code Review • HTML Artifacts
Annotate plans, specs, markdown, and HTML before implementation. Review diffs and PRs. Send feedback to your agent.
  
  
  
  
  
  
  
  
Watch the og demo · Installation guide · Official site · Visual HTML Skills · Herdr Annotate
Plannotator
Plannotator is a local, browser-based review surface for AI coding agents: Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode, Kiro, Droid, Amp, and Pi.
**It plugs directly into your agent** through its hooks and commands. When the agent proposes a plan, html, or finishes writing code, the work opens in your browser and you mark it up, comment, and send feedback directly to the agent for it to act on it.
Review documents, plans, and agent messages
Annotate plans, specs, messages, html, then send the feedback to your agent.
Demo: Plan review with Pi
Code Review
Review local changes or remote PRs. Comment on diffs, suggest code. Your comments go back to the agent. Works with Git, GitButler, Jujutsu (jj), Perforce (p4), GitHub, and GitLab.
AI built in: ask AI about anything you're reviewing, or launch AI reviews that post comments to the diff.
Annotate HTML Artifacts
Herdr Annotate: Plannotator in the Terminal
  
Herdr Annotate brings Plannotator-style review to the terminal: annotate terminal text, review whole Markdown documents and your coding agent's replies inside Herdr, and send the feedback straight back to the agent as its next message. Works with Claude Code, Codex, Pi, Copilot CLI, and Droid replies. Annotations are saved in the Plannotator data directory, so terminal reviews and app reviews compound.
Prefer it standalone? Plannotator TUI powers the document review and runs without Herdr: brew install plannotator/tap/plannotator-tui.
---
Commands
On Codex, swap the slash commands for !plannotator … (e.g. !plannotator review) or the $plannotator-* skills.
Annotate
Need a realistic document to try? Copy the product requirements document template and filled example as Markdown.
Code review
GitButler users can review the whole workspace, one stack, or one branch layer. See the GitButler workflow guide.
Plan mode
No command needed. Plan mode is wired in through each harness's hooks. Any time your agent creates a plan, the markdown review surface opens for you.
CLI
---
Privacy and network behavior
Plannotator does not collect usage telemetry or analytics. Plans, diffs, annotations, drafts, history, and configuration stay local by default.
Each plan review, annotate, archive, share-portal, and code-review app surface checks GitHub for the latest Plannotator release when it loads. This sends no plan or review content and gives the Plannotator project owner no usage analytics, although GitHub receives an ordinary request. There is currently no opt-out setting for the release check. Local Git code review can also query the configured origin with git ls-remote to detect the default branch and a stale baseline; it does not send the local diff. That remote query runs when the review opens, when the page loads its diff, when you switch the diff type or base (including the "Diff out of date · Refresh" button), and when you press Fetch — never on a timer, so an idle review page makes no network calls. Turn it off entirely with plannotator review --no-git-remote-check, PLANNOTATOR_GIT_REMOTE_CHECK=0, or { "gitRemoteCheck": false } in ~/.plannotator/config.json; the compare target then comes from local refs only and the "behind GitHub" banner never appears.
Content leaves the local workflow only when a network feature needs it:
- URL annotation fetches the requested site, through Jina Reader by default for public pages or directly when Jina is disabled or unavailable.
- GitHub and GitLab review uses your authenticated CLI and Git remote to retrieve PR or MR data.
- Ask AI and review agents send the selected question and relevant plan, document, repository, or diff context to your configured provider. When Ask AI is answered by the agent session that opened Plannotator ("Ask this session"), the question goes to that session instead.
- Sharing sends the complete link to whoever or whatever service you use to deliver it. Encrypted short links upload ciphertext to the paste service.
Source
awesome · https://github.com/backnotprop/plannotator
Browse by field
MCP servers
added
yesterday

More in MCP servers

All 5,525 in MCP servers →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index