MCP server for Overleaf integration, enabling LaTeX document editing and git operations on Overleaf projects
Strong tool definitions with complete schemas and descriptions across all 16 tools. Naming follows verb_noun convention consistently (list_, read_, get_, write_, str_replace, insert_, add_, replace_, remove_). All tools have descriptions (avg 150 chars, within 10-1024 baseline). Input schemas are fully specified with types and required fields. However, output schemas are not documented, LLMs cannot predict response structure. Error handling lacks recovery guidance and categorization. No tool annotations (readOnlyHint/destructiveHint) despite clear read/write distinction. Parameter descriptions are adequate but could be more prescriptive about constraints and formats.
Add a new bibliography entry to a .bib file. Commits and optionally pushes to the remote.
Get everything from \end{document} (inclusive) to the end of the file. Returns an empty string if \end{document} is absent (e.g. \input'd files). Note: bibliography commands (\bibliography{}, \bibliographystyle{}, \printbibliography) appear before \end{document} and are part of the last section's content range — use str_replace to edit them. Only applicable to .tex files.
Get everything before the first sectioning command in a .tex file: the document class declaration, package imports, and custom command definitions. Returns the full file content if the file contains no sections. Only applicable to .tex files.
Get the full content of a specific section in a .tex file. If the same section title appears under multiple parent sections, supply parentTitle to disambiguate. Only applicable to .tex files.
Get all sections from a .tex file as a hierarchical tree. Each node includes its type (section, subsection, etc.), title, character offset, the text content immediately following that heading (not including children), a 100-character preview, and a children array of nested sections. Use this for document structure overview and to identify which section to read or edit next. Only applicable to .tex files.
Output schemas not documented. LLMs cannot predict response structure for any tool, forcing them to guess what fields are returned and breaking tool chaining.
Write tools lack error handling guidance. No recovery instructions for common failures (file not found, merge conflict, push rejected). Agents cannot self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Insert text after a target substring in a file. Commits and optionally pushes to the remote.
Insert text before a target substring in a file. Commits and optionally pushes to the remote.
List files in an Overleaf project
Show recent git commits for the project, optionally filtered by file path and/or time range. Each entry includes the commit hash, date, author, and subject.
List all configured Overleaf projects
Read a file from an Overleaf project
Remove a bibliography entry from a .bib file by its citation key. Commits and optionally pushes to the remote.
Replace an existing bibliography entry in a .bib file by its citation key. Commits and optionally pushes to the remote.
Replace a substring in a file. Useful for targeted edits. Commits and optionally pushes to the remote.
Write or overwrite a file in an Overleaf project. Commits and optionally pushes to the remote.
Replace the content of a section in a .tex file. If the same section title appears under multiple parent sections, supply parentTitle to disambiguate. Only applicable to .tex files.
No tool annotations despite clear read/write distinction. Write tools should have destructiveHint=true; read tools should have readOnlyHint=true. Helps agents reason about side effects.
Parameter descriptions lack format/constraint details. E.g., 'extension' says 'optional, e.g. ".tex"' but should specify format (must start with dot, valid LaTeX extensions). Invites invalid input.
No confirmation/dry-run for destructive operations. write_file, str_replace, and remove_bib_entry can corrupt documents. Should support a dry_run parameter or require explicit confirmation.