An MCP server for Overleaf that lets a Claude or other agent navigate projects, read/edit .tex files, compile, and work with review-panel comments — over Overleaf's , the same channel the official...
概览
An MCP server for Overleaf that lets a Claude or other agent navigate projects, read/edit .tex files, compile, and work with review-panel comments — over Overleaf's , the same channel the official web editor uses. The one feature no existing Overleaf MCP can deliver: when a project has enabled, the agent's edits appear as , the same way a human collaborator's edits do. You and your collaborators can accept or reject each suggestion. You can also ask the agend to accept/reject them (e.g. "accept all suggestions about typos"). The three existing Overleaf MCPs (mjyoo2/overleafmcp, YounesBensafia/overleaf-mcp-server, GhoshSrinjoy/Overleaf-mcp) all write through Overleaf's , which has two problems for collaborative academic work: 1. Commits show up in Overleaf with delay (the bridge polls). 2. Git-bridge writes — even when track-changes mode is on, edits land as direct overwrites, not as suggestions for review. The overleaf-workshop VSCode extension already uses Overleaf's Socket.
README
以下为原文 README 节选，完整内容请查看原文。
overleaf-mcp
An MCP server for Overleaf that lets a Claude or other agent navigate projects, read/edit .tex files, compile, and work with review-panel comments — over Overleaf’s real web/Socket.IO API, the same channel the official web editor uses.
The one feature no existing Overleaf MCP can deliver: when a project has track-changes enabled, the agent’s edits appear as pending suggestions in the Review panel, the same way a human collaborator’s edits do. You and your collaborators can accept or reject each suggestion. You can also ask the agend to accept/reject them (e.g. “accept all suggestions about typos”).
Why a new MCP
The three existing Overleaf MCPs (mjyoo2/overleafmcp, YounesBensafia/overleaf-mcp-server, GhoshSrinjoy/Overleaf-mcp) all write through Overleaf’s Git bridge, which has two problems for collaborative academic work:
- Commits show up in Overleaf with delay (the bridge polls).
- Git-bridge writes bypass tracked changes entirely — even when track-changes mode is on, edits land as direct overwrites, not as suggestions for review.
The overleaf-workshop VSCode extension already uses Overleaf’s Socket.IO API rather than Git, but doesn’t yet emit tracked changes (issue #94).
overleaf-mcp solves both: a minimal Socket.IO 0.9 client over fetch + ws@8, plus the meta.tc ID seed on applyOtUpdate that flips Overleaf’s server-side RangesTracker into track-changes mode.
Status
Working end-to-end against overleaf.com — 16 tools, tracked-changes edits and review-panel comments both verified. Published on npm as @netique/overleaf-mcp.
Tools
Every project-scoped tool also takes an optional project_id — see Project selection across MCP sessions.
| Tool | Description |
|---|---|
ping |
Health check. Does not contact Overleaf. |
list_projects |
Lists projects on the configured account, sorted by most recently updated. Supports name_contains, include_archived, include_trashed, limit. |
open_project |
Joins a project’s real-time session and caches its file tree. Returns rich metadata: root_doc_path, compiler, spell_check_language, public_access_level, owner + members (with privileges), and whether track-changes is on for your user. |
list_files |
Lists the file tree of the open project (cached, no network). Filter by kind and path_contains. |
read_file |
Reads a doc (returns text + OT version + a summary of tracked changes / comments) or a binary file (base64 + MIME). path is optional — defaults to the project’s root doc. |
安装
npx -y @netique/overleaf-mcp配置
{
"mcpServers": {
"overleaf": {
"command": "npx",
"args": ["-y", "@netique/overleaf-mcp"]
}
}
}