overleaf-mcp-server
Related Servers
Alternatives to overleaf-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, edit, upload, compile, and manage projects in a self-hosted Overleaf Community Edition via MCP, while also providing a git remote for cloning and pushing changes.1MIT
- FlicenseBqualityCmaintenanceEnables AI agents to interact with Overleaf projects directly, including creating projects, managing files, and editing documents in real-time using Overleaf's native Operational Transformation protocol.101-
- AlicenseNot gradedqualityCmaintenanceEnables Claude and AI agents to read and edit Overleaf documents in real time, with support for project listing, document manipulation, LaTeX compilation, and live collaboration.184 npm37MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to read, write, compile, and download LaTeX projects on a self-hosted Overleaf instance.10 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients like Claude and Cursor to read, edit, compile, and review Overleaf LaTeX projects through Git integration or optional web mode, including managing files, outlines, comments, and PDF downloads. Also converts Markdown drafts into LaTeX written directly into a project.1726 npm5MIT
- AlicenseAqualityBmaintenanceEnables collaborative LaTeX editing on Overleaf with tracked changes, review comments, compilation, file management, and downloads via a single MCP connection.261AGPL 3.0
TDQS
Scored across 16 tools
Each tool targets a distinct resource-action pair: projects, files/folders, and compilation outputs are clearly separated. Even closely related tools like write_file vs upload_file and compile_project vs get_compile_log are differentiated by explicit text/binary and structured/raw output descriptions.
All tool names follow a consistent snake_case verb_noun pattern (list_projects, create_folder, move_entity, compile_project). The use of list, get, create, write, upload, move, delete, etc. is predictable and maps cleanly to CRUD and domain actions.
16 tools is one above the typical 15-tool sweet spot, but each tool covers a meaningful project, file, or compile operation without redundancy. The count feels slightly heavy but remains well-scoped for a full Overleaf workflow.
The surface covers project lifecycle, file/folder management, and compilation well. Minor gaps exist: there is no unarchive/restore operation, no rename for files/folders, and no single-file download, but these are workaroundable via export_project or move_entity.