Overleaf MCP Server
LaTeX projects on Overleaf via Git for reading, writing, and parsing documents.
Data last scanned 2 days ago · Reviewed 2 months ago
Overview
This server integrates Overleaf projects into MCP-compatible clients using Git. It allows AI models to directly read LaTeX source files, analyze document structures like sections and subsections, and extract content for specific research or drafting needs. The server supports managing multiple Overleaf projects through a local JSON configuration file. Users can provide project IDs and Git tokens to perform file management operations, including listing files and writing updates directly back to their Overleaf repositories.
Our verdict
With a security score of 40/100, this server carries a high risk level. The lack of an authentication review and its status as a community-maintained project mean users should exercise caution when providing Git tokens. It is recommended only for users who understand the implications of granting write access to their Overleaf projects via a third-party MCP implementation.
- Supports multi-project management via local configuration
- Uses minimal supply chain with only one direct dependency
- Parses LaTeX structure for targeted content extraction
- High risk due to unreviewed authentication methods
- Not maintained by the official Overleaf vendor
- Read-only operational mode has not been verified
Setup
{
"mcpServers": {
"overleafmcp": {
"args": [
"-y",
"@mjyoo2/overleaf-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›How do I obtain the required Overleaf credentials?
The Project ID is found in your Overleaf project URL, and the Git Token can be generated in your Overleaf Account Settings under the Git Integration section.
›Can I manage multiple Overleaf projects at once?
Yes, you can define multiple projects in a 'projects.json' configuration file and reference specific projects by name using the 'projectName' argument in tool calls.
›Is there a way to store my Git token without including it in the Claude Desktop configuration file?
Yes, you can set an 'OVERLEAF_GIT_TOKEN_FILE' environment variable pointing to a local file containing your token, which will be read once at startup.
›How does the server determine which project to use if I don't specify one?
If you are using a multi-project setup and omit the 'projectName' in a tool call, the server will default to the project labeled 'default' in your configuration.
›What is the configuration precedence if I have both environment variables and a configuration file?
The server follows a specific order of precedence where environment variables take priority; if both are set, the environment variables will shadow the file-based configuration.
›Do I need to install the package locally to use it with Claude Desktop?
No, you can use 'npx' in your Claude Desktop configuration to run the server directly without manual cloning or local npm installation.
Alternatives
Badge
Maintain this server? Add the live badge to your README.