fix-my-comments-mcp
This server enables AI agents to read and manage Fix My Comments tasks (VS Code comment threads) via the Model Context Protocol, automatically scoped to the current Git repository and branch.
List open tasks (
list_open_tasks): Retrieve all open tasks in the current workspace, optionally filtered by file path.Get task thread (
get_task_thread): Fetch a specific task and its full message history in chronological order.Post agent reply (
post_agent_reply): Append an AI-generated reply to a task thread, including agent ID/name, a summary of actions taken, and an optional list of changed files.Set task status (
set_task_status): Mark a task asresolvedorrequires_review, optionally providing a reason.
Additional behaviors:
Zero configuration — automatically scopes to the current Git repo and branch.
Prevents writes to comment threads that have become outdated due to source code line changes.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fix-my-comments-mcp list open tasks in src/main.ts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fix-my-comments-mcp
MCP server for Fix My Comments — exposes local VS Code comment threads to AI agents (Claude Code, Cursor, Windsurf, etc.) through the Model Context Protocol.
The server is intentionally small: it reads and writes the same JSON files as the VS Code extension, under ~/.fixmycomments/<repo>-<hash>/<branch>/, and communicates over stdio.
How it works
Zero config — the server derives storage from
process.cwd()and the current Git branch.Repo + branch scoped — comments are isolated by repository and branch.
Shared with the extension — the VS Code extension and MCP server read/write the same
threads.jsonandmessages.jsonfiles.Stale-comment safe — the server checks anchored line hashes against the current workspace file. Outdated threads are hidden by default and write actions are blocked.
Run your agent from inside the repository root. If you start it from another directory, the server will resolve a different storage path.
Related MCP server: tai-mcp-github
Installation
Option A: Global install via npm (recommended)
npm install -g fix-my-comments-mcpThen add it to Claude Code:
claude mcp add fix-my-comments --scope user -- fix-my-commentsOption B: Local dev via npm link
git clone <this-repo>
cd fix-my-comments-mcp
npm install
npm run build
npm link
claude mcp add fix-my-comments --scope user -- fix-my-commentsAvailable Tools
Tool | Description |
| List open, non-outdated threads for the current branch. Optionally filter by file path. |
| Get a thread and its messages; use |
| Get one comment/message with its thread summary and position. |
| Get one message plus N messages before/after it to avoid loading a whole long thread. |
| Append an AI reply, optionally tied to a message and optionally posted as a code suggestion. |
| Resolve or reopen a thread. |
| Check or uncheck a task message. |
| Add an emoji reaction to a message. |
| Remove an agent's emoji reaction from a message. |
Token-efficient reads
Agents should prefer the smallest read tool that answers the question:
Use
list_open_threadsto discover work.Use
get_messagewhen a message id is already known.Use
get_message_contextto fetch a small window around one message.Use
get_threadonly when the whole thread is needed, or passmessageLimitfor the latest messages.
Outdated thread behavior
By default, the server filters out and blocks writes to outdated threads whose anchored line changed.
list_open_threadsexcludes outdated threads unlessincludeOutdated=true.get_thread,get_message, andget_message_contextrequireincludeOutdated=trueto inspect stale comments.post_agent_reply,set_task_message_status,add_reaction, andremove_reactionare blocked on outdated threads.
Requirements
Node.js 18+
The Fix My Comments VS Code extension installed and active in the project
Available Tools
4 toolsget_task_threadA
Get a task and its full message thread in chronological order.
Inputs: taskId (required).
list_open_tasksA
List all open Fix My Comments tasks for the current workspace and branch. Optionally filter by file path.
Inputs: filePath.
post_agent_replyB
Append a reply to a task thread as an AI agent and record execution metadata.
Inputs: taskId (required), content (required), agentId (required), agentName (required), +3 more.
set_task_statusB
Set a task status. Agents may set resolved or requires_review.
Inputs: taskId (required), status (required), reason.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool addresses a distinct operation: retrieving a thread, listing tasks, posting a reply, and setting status. There is no role overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With 4 tools, the server is tightly scoped to its purpose of managing comment review tasks. No tool seems extraneous.
The set covers core workflows (list, view, reply, update status). Lacking create/delete tools, but those may be handled externally or implicitly supported.
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP Server for an Agent Task Marketplace
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for managing a project backlog as Markdown files in Git, enabling AI agents to read, create, and update tasks programmatically.2MIT
- FlicenseAqualityDmaintenanceA minimal MCP server that exposes a focused set of GitHub PR review tools to AI agents, enabling PR listing, detail retrieval, comment viewing, and thread management.5-
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
- AlicenseNot gradedqualityDmaintenanceMulti-AI collaboration MCP server enabling message passing, code review workflows, shared todo lists, and agent management with authentication and role-based access.21 npmMIT