olcli
Related Servers
Alternatives to olcli
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables reading and editing self-hosted ShareLaTeX/Overleaf projects from an MCP client, including file search, section outlining, versioned writes, and compilation diagnostics.11MIT
- AlicenseAqualityCmaintenanceEnables collaborative LaTeX editing on Overleaf with tracked changes, review comments, compilation, file management, and downloads via a single MCP connection.261AGPL 3.0
- AlicenseAqualityCmaintenanceEnables AI agents to read, write, compile, and manage Overleaf projects through MCP, including file operations, project administration, and LaTeX compilation diagnostics.16MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Overleaf projects, enabling project listing, file reads, LaTeX section discovery, and revision-guarded writes through natural language.AGPL 3.0
- AlicenseBqualityCmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.449 PyPI66MIT
- AlicenseAqualityDmaintenanceMCP server for managing academic LaTeX projects in Overleaf: create projects, transfer files, compile documents, inspect compiler output, and download PDFs.1620 npmMIT
TDQS
Scored across 22 tools
Most tools map to distinct resource+action pairs, but three compilation tools (compile, download_pdf, compile_with_outputs) heavily overlap, and get_project_info vs get_entities both return file/doc listings with only a shape difference. rename_project vs plan_project_renames is also a trap: one renames, the other explicitly never renames and requires a terminal command, which is easy for an agent to misread.
Almost everything follows a snake_case verb_noun pattern (list_projects, push_file, accept_tracked_changes, resolve_comment), with only the bare 'compile' breaking the convention. Naming is readable and predictable overall.
22 tools is heavy for what is essentially project/file/compile/review management; the compile trio and the two listing tools could be consolidated. Each tool does correspond to a real operation, so it is borderline rather than bloated.
Core lifecycle is covered (create/pull/push/list/diff, comments, tracked changes), but there is no delete_project despite create_project hinting one exists, no tool to list tracked-change IDs even though accept/reject require them, and no way to edit or delete a comment. These gaps create dead ends for common workflows.