overleaf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| overleaf_whoamiA | Check whether OVERLEAF_COOKIE is set and still a valid, logged-in session. |
| overleaf_list_projectsA | List your Overleaf projects (id, name, owner, last-updated timestamp). |
| overleaf_pullA | Download an Overleaf project and extract it into dest_dir (overwrites existing files). |
| overleaf_push_fileA | Upload or overwrite a single file in an Overleaf project. Creates any missing remote folders in remote_path. Joins the realtime channel to resolve folder ids, so this is slower than overleaf_pull. |
| overleaf_push_dirA | Push every locally-changed file under local_dir into an Overleaf project. Diffs local files against the current remote content (byte-for-byte) and uploads only what differs or is new locally. Does not delete remote files that were removed locally — use overleaf_delete_file for that. |
| overleaf_delete_fileB | Delete a file from an Overleaf project. |
| overleaf_compileA | Trigger a compile and return its status (and the error log on failure). |
| overleaf_download_pdfB | Compile an Overleaf project and download the resulting PDF to dest_path. |
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 8 tools
Most tools serve distinct purposes, but overleaf_compile and overleaf_download_pdf both involve compilation, and overleaf_push_file / overleaf_push_dir are closely related. Descriptions clarify the differences, so ambiguity is low.
All tools share the overleaf_ prefix and use lowercase snake_case, but the pattern is not perfectly uniform: some are verb_object (delete_file, list_projects) while others are just verbs (compile, pull). This is mostly consistent and predictable.
With 8 tools, the server is well-scoped for its purpose, covering essential Overleaf operations without unnecessary redundancy. The count is appropriate for a focused integration.
Core workflows like pulling, pushing, compiling, and downloading PDFs are covered, but there is no way to create or delete projects, and no direct file listing (only via pull). These gaps may require workarounds.