Overleaf MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OVERLEAF_GIT_TOKEN | No | Your Overleaf Git token (starts with olp_) | |
| OVERLEAF_PROJECT_ID | No | The project ID from the Overleaf URL (https://www.overleaf.com/project/[PROJECT_ID]) | |
| OVERLEAF_PROJECT_NAME | No | Optional display name for the project | |
| OVERLEAF_GIT_TOKEN_FILE | No | Path to a file containing the Overleaf Git token (alternative to OVERLEAF_GIT_TOKEN) | |
| OVERLEAF_PROJECTS_CONFIG | No | Path to a projects.json file for multiple projects |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesC | List all files in an Overleaf project |
| read_fileC | Read a file from an Overleaf project |
| get_sectionsC | Get all sections from a LaTeX file |
| get_section_contentC | Get content of a specific section |
| status_summaryC | Get a summary of the project status using default credentials |
| list_projectsB | List all available projects |
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 6 tools
Each tool has a clearly distinct purpose targeting different resources or actions: list_projects (projects), list_files (files within a project), read_file (content of a file), get_sections (sections within a file), get_section_content (content of a specific section), and status_summary (project overview). There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern with snake_case: list_projects, list_files, read_file, get_sections, get_section_content, and status_summary. The verbs (list, read, get) are appropriate and predictable, making the set easy to navigate.
With 6 tools, this server is well-scoped for managing Overleaf projects, covering core operations like listing projects/files, reading content, and getting summaries. The count is appropriate—neither too sparse nor bloated—for the domain of LaTeX project management.
The tool set provides good coverage for reading and listing operations in Overleaf projects, but there are minor gaps in write/update capabilities (e.g., no tools for creating or editing files/sections). Agents can work around this for read-only tasks, but full lifecycle management is incomplete.