A
licenseNot graded
qualityC
maintenanceEnables Claude, Cursor, or any MCP client to pull an Overleaf project, edit .tex files, check references, compile when a TeX binary is installed, and push changes back.
MIT
Overleaf MCP Server
by juho127
Related Servers
Alternatives to Overleaf MCP Server
No user-submitted related servers found.
Related Servers
- 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 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
- AlicenseAqualityAmaintenanceEnables access to Overleaf LaTeX projects through Git integration, allowing users to read files, analyze document structure, extract sections, and manage multiple projects through natural language commands.216 npm10MIT
- 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
- AlicenseBqualityBmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.442 PyPI64MIT
TDQS
A3.5/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: clone_project for initial setup, configure_auth for credentials, get_status for local state, pull_changes for syncing from remote, and push_changes for syncing to remote. The actions and targets are well-defined and unambiguous.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case: clone_project, configure_auth, get_status, pull_changes, push_changes. The naming is predictable and readable throughout the set.
Tool Count5/5
With 5 tools, this server is well-scoped for managing Overleaf projects locally. Each tool earns its place by covering essential operations for cloning, authentication, status checking, and bidirectional syncing, without being too sparse or bloated.
Completeness4/5
The toolset covers core workflows for local Overleaf project management: setup (clone, auth), status checking, and syncing (pull, push). Minor gaps might include project creation or deletion on Overleaf, but agents can work around this by using existing tools for most common tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues