F
licenseA
qualityB
maintenanceEnables Claude to read and edit Overleaf projects via the git bridge, with compile-gated writes to ensure safety.
10
-
mcp-server-overleaf
by yangzichao
Related Servers
Alternatives to mcp-server-overleaf
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.6125 npm312MIT
- 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.215 npm10MIT
- 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
- AlicenseBqualityBmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.4153 PyPI64MIT
TDQS
A4.4/5.0
Scored across 18 tools
Disambiguation4/5
Each tool has a distinct resource+action, and descriptions explicitly cross-reference alternatives (e.g. list_files vs project_summary vs search_project, read_file vs read_section). Some mild overlap exists between read_file/read_section and show_diff/project_status/sync_project, but the descriptions resolve the boundaries clearly.
Naming Consistency4/5
Nearly all tools follow a verb_noun or verb pattern (read_file, list_files, edit_section, push_changes, compile_project). The only deviations are the noun_noun pair project_summary and project_status, which are still readable and predictable.
Tool Count4/5
18 tools is slightly on the heavy side but each earns its place across the read/edit/sync/compile/publish lifecycle of a real Overleaf client. No obvious redundant tools inflate the count.
Completeness4/5
The surface covers the full editing lifecycle: discovery, read, search, edit, write, move, delete, diff, status, sync, compile, and push. Minor gaps remain (project creation, history/versioning, PDF export, collaborator management), but core workflows have no dead ends.
Maintenance
ActivityNo data
ResponsivenessNo issues