Typleaf MCP Server
Related Servers
Alternatives to Typleaf MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants and agents to explore, read, live-edit, patch, create, and delete files across projects on a self-hosted Overleaf Community Edition deployment, with OT-safe edits that sync instantly to open browser tabs. It also triggers server-side LaTeX compilations, returns parsed errors and warnings from the log for auto-debugging, and delivers authenticated PDF download links.MIT
- AlicenseAqualityAmaintenanceEnables an AI assistant to read and edit online Typst projects, including managing files, projects, share links and members, and threaded comments, while preserving concurrent browser edits. Also compiles documents locally to PDF, PNG or SVG with file:line diagnostics and inline page previews.26MIT
- 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
- AlicenseAqualityBmaintenanceEnables local AI agents to discover projects and read, upload, update, and delete files in a self-hosted collaborative LaTeX/Markdown writing platform, plus maintain a local mirror with git-style pull, push, and status synchronization.14MIT
- AlicenseNot gradedqualityBmaintenanceConnects an AI assistant to a user's account so they can search a LaTeX template library, create and edit projects and their files, and compile documents to PDF with errors reported by file and line. Includes tools for listing projects, setting the TeX engine, and keeping version history when a file is replaced.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to read, write, and compile LaTeX projects locally, view PDF pages as images, and manage project files, with live updates reflected in a web-based editor.-
TDQS
Scored across 29 tools
Most tools target a distinct action/resource combination, and the descriptions clearly separate edit_file, rewrite_file, update_section, and write_files. status_summary, project_info, and get_sections have some overlap in reporting headings or project overview, but the descriptions provide enough guidance to choose correctly.
The tool set predominantly follows a clear verb_noun pattern such as list_files, create_file, delete_file, and download_pdf. A few noun-style names like status_summary, project_info, and section_page_map are minor deviations that do not obscure the overall pattern.
With 29 tools, the surface exceeds the 25+ threshold and feels heavy for an agent to navigate. Many tools are individually justified, but there are several closely related variants around editing, downloading, and PDF mapping that increase selection cost.
The core document lifecycle is well covered: project creation, file CRUD, editing, compilation, PDF/log retrieval, page mapping, citation verification, and git operations. Minor gaps such as deleting or renaming projects and moving files are workaround-able and not central to the primary compile-edit workflow.