overleaf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OVERLEAF_TOKEN | Yes | Your Overleaf git token, generated in Overleaf Account Settings |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_projectA | Open a project and run the safety gate: pull, verify every \usepackage resolves locally, then baseline-compile each root. Required before any write. |
| outlineA | Map a document's structure with line numbers — sections, figures, labels, includes. Use before reading; far cheaper than the whole file. |
| readA | Read a file, line-numbered. lines='150-190' reads a range; omit for all. Prefer a range guided by outline. |
| grepB | Regex-search the project, returning file:line: match. |
| filesC | List .tex files, marking which are roots. |
| compileA | Compile the root owning |
| renderA | One page of the compiled PDF as an image, for layout only — float placement, overlap, figure sizing. Expensive: try compile() warnings first, and use read() for anything about the text itself. |
| editA | Replace an exact snippet, then compile and push. |
| writeA | Create or overwrite a file, then compile and push. For new documents and whole-file rewrites; prefer edit() for changes to an existing document. |
| add_assetA | Copy a local image or binary into the project, then push. Compiles only the roots that actually reference it — an unreferenced file cannot break a build. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a distinct purpose: project setup, structural navigation, content search, precise edits, whole-file writes, compilation, rendering, and asset additions. There is no meaningful overlap between tools that would cause an agent to select the wrong one.
Names are readable and consistently lowercase, but the pattern is mixed. add_asset and open_project follow verb_noun, while outline, read, grep, files, compile, render, edit, and write are bare commands, making the naming convention less predictable.
Ten tools is well-scoped for an Overleaf/LaTeX workflow: the server covers project setup, reading, searching, editing, writing, compilation, asset management, and visual rendering without unnecessary clutter.
The core workflow is well covered, including open, explore, read, search, edit, write, compile, render, and add assets. The most notable gap is the absence of delete/rename operations, but most agents can work around this for typical LaTeX editing tasks.