F
licenseB
qualityC
maintenanceEnables 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.
10
-
mcp-overleaf
by GomFal
Related Servers
Alternatives to mcp-overleaf
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, edit, and compile LaTeX documents in Overleaf projects with tracked changes via the Model Context Protocol.3MIT
- 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
- AlicenseAqualityCmaintenanceEnables AI assistants to read, edit, and compile LaTeX projects on Overleaf using session cookie authentication, bypassing the need for a paid plan.8MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read, write, compile, and manage Overleaf projects through MCP, including file operations, project administration, and LaTeX compilation diagnostics.165 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to read and edit Overleaf projects through the official git bridge, with local staging of changes and conflict detection before publishing.69 npmMIT
TDQS
A3.7/5.0
Scored across 10 tools
Disambiguation4/5
Most tools target clearly distinct actions across session, file, compile, and publish workflows. The only minor ambiguity is between connector_status and workflow_status, both of which report state but from different perspectives.
Naming Consistency4/5
The majority of tool names follow a clear verb_noun pattern like begin_edit_session, read_report_file, and confirm_publish. The exceptions are connector_status and workflow_status, which use an object_status pattern, creating a small inconsistency.
Tool Count5/5
Ten tools is well-scoped for a Git-to-Overleaf synchronization and publishing workflow. Each tool contributes a distinct step in the lifecycle without unnecessary redundancy.
Completeness4/5
The core workflow is well covered: session lifecycle, file read/write, compilation, preview, and publish confirmation are all present. Minor gaps include no explicit delete-file or conflict-resolution tool, though the write tool and status reporting partially mitigate this.
Maintenance
ActivityMaintained
ResponsivenessNo issues