olcli
Related Servers
Alternatives to olcli
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables collaborative LaTeX editing on Overleaf with tracked changes, review comments, compilation, file management, and downloads via a single MCP connection.261AGPL 3.0
- AlicenseAqualityBmaintenanceEnables AI agents to read, write, compile, and manage Overleaf projects through MCP, including file operations, project administration, and LaTeX compilation diagnostics.163 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for interacting with Overleaf projects, enabling project listing, file reads, LaTeX section discovery, and revision-guarded writes through natural language.AGPL 3.0
- AlicenseBqualityBmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.442 PyPI64MIT
- AlicenseAqualityCmaintenanceMCP server for managing academic LaTeX projects in Overleaf: create projects, transfer files, compile documents, inspect compiler output, and download PDFs.162 npmMIT
- 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
This server cannot be deployed
TDQS
Scored across 21 tools
Most tools have distinct resource+action targets, and rename_project explicitly disambiguates itself from rename_entity. However, the compile trio (compile, download_pdf, compile_with_outputs) all compile and differ mainly in output destination, and get_project_info (file tree) vs get_entities (flat list) vs pull_project (full zip) overlap enough to require reading descriptions carefully.
Almost everything follows a snake_case verb_noun pattern (list_projects, push_file, resolve_comment, rename_entity, plan_project_renames). Minor deviations are the bare verb 'compile' and verb-only 'download_pdf', which are still readable and unambiguous.
21 tools is on the heavy side but the domain genuinely spans projects, files, comments, tracked changes, compilation, and bulk rename planning, and each tool maps to a real operation. A few could be consolidated (compile variants), keeping it just under 'well-scoped'.
Core lifecycle is covered (list/create/rename projects, pull/push/download/delete/rename files, comment lifecycle, compile, accept/reject tracked changes). But accept_tracked_changes and reject_tracked_changes require change IDs with no corresponding list_tracked_changes tool, and there is no move-entity or comment delete/reopen operation, leaving notable gaps.