MCP server to read, edit, compile, and commit LaTeX in a git-hosted project (Overleaf, GitHub, any git remote).
Server has 27 tools with consistent naming (verb_noun pattern) and descriptions present for all. However, parameter schemas are largely inferred from code rather than explicitly visible in the provided samples. Only serverInfo.ts shows explicit schema definition with Zod. Most tool files are not provided, making it impossible to verify input/output schemas comprehensively. Descriptions are adequate (50-200 chars typical) but lack LLM-optimized guidance on when to use each tool vs. similar ones. Error handling and recovery guidance are not evident in samples. Destructive operations (delete_file, discard, reset_to_remote) lack confirmation patterns.
Add a citation to a LaTeX project's bibliography.
Check for undefined or unused citations in a LaTeX project.
Commit changes to a LaTeX project.
Compile a LaTeX project to PDF.
Open a loopback page for entering git credentials.
Delete a file from a LaTeX project.
Show changes in a LaTeX project.
Discard uncommitted changes in a LaTeX project.
Run diagnostics on the local LaTeX toolchain.
Input/output schemas not visible for 26 of 27 tools. Only serverInfo.ts shows explicit Zod schema definition. Cannot verify parameter types, constraints, or output structure for the vast majority of tools.
Destructive operations (delete_file, discard, reset_to_remote) lack confirmation or dry-run patterns. Agents can irreversibly delete files or reset repositories without explicit user approval.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2025-06-18+ | v2 |
Edit a file in a LaTeX project using line-based edits.
List all comments on a LaTeX project.
List files in a LaTeX project.
List all registered LaTeX projects available in the workspace.
List all references in a LaTeX project's bibliography.
List available skills that can be invoked.
Synchronize a project with its remote repository.
Push commits to the remote repository.
Read the contents of a file in a LaTeX project.
Register a new LaTeX project from a git URL or local directory.
Reset a LaTeX project to match the remote repository.
Mark comments as resolved.
Search for academic references in DBLP.
Report the web-latex-mcp server version and runtime configuration (workspace root, whether the workspace is local to the launch dir, whether the clone dir was git-excluded from the host repo, and the configured compiler). Use this to confirm which version of the MCP server is running.
Store credentials for accessing git repositories.
Show the git status of a LaTeX project.
Open a viewer for the compiled PDF and manage comments.
Write or create a file in a LaTeX project.
Credential handling via set_credential and credential_portal may expose secrets. No evidence of server-side secret injection or vault integration. Credentials stored in workspace could leak into logs.
Generic tool names (status, diff, viewer, doctor) lack clarity on what they operate on. 'status' could mean git status, compilation status, or project status. Ambiguous names increase LLM selection errors.
No evidence of pagination support in list_* tools (list_projects, list_files, list_comments, list_references). Large result sets could exhaust context window.