A
licenseNot graded
qualityB
maintenanceEnables editing Overleaf projects from Claude, with tools to list, read, edit, and sync files via Git.
MIT
overleaf-multi-mcp
by NVCLong
Related Servers
Alternatives to overleaf-multi-mcp
No user-submitted related servers found.
Related Servers
- 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.44 npm19MIT
- FlicenseAqualityBmaintenanceEnables Claude to read and edit Overleaf projects via the git bridge, with compile-gated writes to ensure safety.10-
- AlicenseNot gradedqualityBmaintenanceConnects Claude/ChatGPT to Overleaf projects via the Git integration, enabling read, edit, write, and file management through natural language commands.2AGPL 3.0
- AlicenseBqualityCmaintenanceProvides access to Overleaf projects via Git integration, allowing Claude and other MCP clients to read LaTeX files, analyze document structure, and extract content.6153 npm265MIT
- AlicenseBqualityBmaintenanceConnects Claude to your Overleaf account to manage LaTeX projects, edit files, compile, and retrieve PDFs.192MIT
TDQS
A3.7/5.0
Scored across 17 tools
Disambiguation5/5
Each tool has a clearly distinct role: project sync/search/status, workspace setup and git operations, file and LaTeX section access, and version management. Even similar-sounding tools like sync_projects and list_projects are differentiated by description (refresh vs. view cached data).
Naming Consistency4/5
Most tools follow a clear verb_noun snake_case pattern (sync_projects, list_files, write_section). Two status tools (session_status, status_summary) are noun_noun and setup_local is slightly awkward, but the overall style is consistent and readable.
Tool Count4/5
At 17 tools, this is on the higher end but within reason given the server's dual focus on Overleaf project management and local git-synced workspaces. Each tool covers a distinct need, though a few could potentially be merged (e.g., status_summary and session_status) without significant loss.
Completeness4/5
The tool surface covers the essential lifecycle: project discovery, workspace setup, local editing, diff/push, version history/rollback, and LaTeX-aware reading/writing. Missing operations like project creation/deletion are likely outside the intended scope (session-based account sync), so the core workflows are well-supported.
Maintenance
ActivitySlowing
ResponsivenessNo issues