Overleaf MCP Server
Integrates with Overleaf's Git feature to manage Overleaf projects, including cloning projects, pulling changes, pushing edits, checking repository status, and configuring Git authentication.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Overleaf MCP Server clone project 65a1b2c3d4e5f6 to /Users/me/research-paper"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Overleaf MCP Server
An MCP server that integrates with Overleaf's Git feature, allowing you to manage Overleaf projects directly from your MCP-enabled environment (like Cursor).
Features
Clone Projects: Clone Overleaf projects to your local machine using the Project ID.
Pull Changes: Sync latest changes from Overleaf to your local copy.
Push Changes: Commit and push your local edits back to Overleaf.
Get Status: Check the status of your local repository (modified files, etc.).
Authentication Management: Securely configure and store your Overleaf Git credentials.
Related MCP server: Overleaf MCP Server
Installation
Clone this repository:
git clone https://github.com/juho127/overleafMCP.git cd overleafMCPInstall dependencies:
npm install"args": ["/path/to/overleafMCP/build/index.js"] } } }
### Other Clients (e.g., Cursor)
For other MCP-supported clients like Cursor:
1. Go to **Settings** > **Features** > **MCP Servers**.
2. Click **+ Add New**.
3. Enter the command to run the server:
- Command: `node`
- Args: `/absolute/path/to/overleafMCP/build/index.js` (Replace with your actual path)
## Usage
### Authentication
Before using the git tools, you should configure your authentication. You can find your Git token in your Overleaf Account Settings.
**Tool**: `configure_auth`
- `email`: Your Overleaf email address.
- `token`: Your Overleaf Git token (or password).
### Cloning a Project
**Tool**: `clone_project`
- `projectId`: The ID from your Overleaf project URL (e.g., `65a1b2c3d4e5f6...`).
- `localPath`: Absolute path where you want to clone the project.
### Managing Changes
- **Pull**: Use `pull_changes` to get updates from Overleaf.
- **Status**: Use `get_status` to see what files you've changed.
- **Push**: Use `push_changes` to save your work back to Overleaf.
## License
MITAvailable Tools
5 toolsclone_projectC
Clone an Overleaf project to a local directory
Inputs: projectId (required), localPath (required), email, token.
configure_authC
Configure global Overleaf credentials
Inputs: email (required), token (required).
get_statusB
Get the status of the local project (git status and diff)
Inputs: localPath (required).
pull_changesC
Pull latest changes from Overleaf for a local project
Inputs: localPath (required).
push_changesC
Commit and push changes to Overleaf
Inputs: localPath (required), message (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: clone_project for initial setup, configure_auth for credentials, get_status for local state, pull_changes for syncing from remote, and push_changes for syncing to remote. The actions and targets are well-defined and unambiguous.
All tools follow a consistent verb_noun pattern with snake_case: clone_project, configure_auth, get_status, pull_changes, push_changes. The naming is predictable and readable throughout the set.
With 5 tools, this server is well-scoped for managing Overleaf projects locally. Each tool earns its place by covering essential operations for cloning, authentication, status checking, and bidirectional syncing, without being too sparse or bloated.
The toolset covers core workflows for local Overleaf project management: setup (clone, auth), status checking, and syncing (pull, push). Minor gaps might include project creation or deletion on Overleaf, but agents can work around this by using existing tools for most common tasks.
Maintenance
Related MCP Connectors
Edit your Overleaf LaTeX projects from Claude and ChatGPT; every change is a real Git commit.
A MCP server built for developers enabling Git based project management with project and personal…
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Persistent AI LaTeX workspace: edit and compile multi-file projects, export publication-ready PDFs.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides access to Overleaf projects via Git integration, allowing Claude and other MCP clients to read LaTeX files, analyze document structure, and extract content.6190 npm362MIT
- AlicenseAqualityBmaintenanceLive search, read, edit and compile access to all your Overleaf projects, signed in with your Overleaf web session, so no Git integration or paid plan is needed. Edits merge with collaborators' typing (optionally as tracked changes), compile errors come back as file:line, and projects can sync to local folders; works with self-hosted Overleaf too.2110MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.449 PyPI66MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, edit, upload, compile, and manage projects in a self-hosted Overleaf Community Edition via MCP, while also providing a git remote for cloning and pushing changes.1MIT