Overleaf MCP Server
Related Servers
Alternatives to Overleaf MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides access to Overleaf projects via Git integration, allowing Claude and other MCP clients to read LaTeX files, analyze document structure, and extract content.6130 npm332MIT
- AlicenseNot gradedqualityAmaintenanceConnects Claude/ChatGPT to Overleaf projects via the Git integration, enabling read, edit, write, and file management through natural language commands.2AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables LLM agents to read and update Overleaf LaTeX papers via git, with tools for reading/writing main.tex and bibliography files.-
- 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.1797 npm5MIT
- AlicenseNot gradedqualityFmaintenanceEnables editing Overleaf projects from Claude, with tools to list, read, edit, and sync files via Git.28 PyPIMIT
- AlicenseAqualityDmaintenanceIntegrates with Overleaf's Git feature to manage LaTeX projects directly from MCP-enabled environments, enabling cloning, syncing, and pushing changes between local machine and Overleaf.512 npmMIT
TDQS
Scored across 21 tools
Most tools have clearly distinct purposes, including separate file, project, search, compile, and history operations. A few pairs such as grep/search and read_file/get_section require reading descriptions to distinguish, but their boundaries are explicitly clarified.
The set predominantly uses consistent snake_case verb_noun names like list_projects, create_project, read_file, and edit_file. A few bare nouns or verbs such as status, search, compile, and history deviate slightly but remain readable and expected.
At 21 tools, the server is somewhat heavy, but the breadth matches Overleaf's project/file/search/compile/history surface. Each tool covers a distinct operation, so the count is reasonable though on the larger side.
Core workflows are well covered: authentication, projects, files, editing, search, compilation, uploads/downloads, and history. Minor gaps exist at the project lifecycle level, such as no delete/rename project or restore history version, but agents can work around them.