criticmarkup
Related Servers
Alternatives to criticmarkup
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to review and revise LaTeX and Markdown manuscripts through anchored, stackable comment threads—listing and reading documents, adding and replying to comments, applying or reverting rewrite candidates, managing thread state, and retrieving baseline diffs via Stdio or Streamable HTTP.MIT
- AlicenseNot gradedqualityDmaintenanceEnables sharing Markdown documents for collaborative review with inline annotations and structured change requests.21 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to search and read linked Markdown notes, queue review questions, capture feedback, and propose edits with stale-edit protection.7Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA local-first markdown review tool with MCP integration, enabling AI and humans to collaboratively annotate documents inline and generate revision prompts.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables interactive review of rendered Markdown documents by selecting passages, queueing line-anchored feedback, and submitting it in one batch to a coding agent that edits the original source file.10 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables anchored comments in Markdown files that AI agents can propose changes for, with human approval before application, all managed via an MCP server.4MIT
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes: reading, targeted single/multiple edits, global replace, creating comments, and replying. However, request_changes applies a single edit despite a plural name that suggests multiple changes, and it overlaps somewhat with replace_multiple at different granularities, so an agent could momentarily confuse them.
All tool names use snake_case with a verb_noun structure (get_md_contents, replace_multiple, request_changes, replace_all, write_comment, reply_to_comment). The naming pattern is predictable throughout; the semantic oddity of request_changes does not break the naming convention.
Six tools is well-scoped for markdown reading, editing, and commenting. Each tool appears to earn its place without excessive granularity or redundancy in count.
Core read/edit/comment-creation workflows are covered, including single, multiple, and global edits plus replying to threads. But the discussion lifecycle is incomplete: there is no resolve, close, or delete comment-thread tool, and no accept/reject lifecycle for CriticMarkup changes, leaving agents at a dead end for closing or cleaning up discussions.