Skip to main content
Each project has its own MCP server, so an AI client on your computer can read and edit the project, compile it and answer its comments. The client signs in with a Git authentication token.
If you see no MCP server card, see MCP Server for your administrator.

Connect a client

1

Open the dialog

Open the project. In the left bar, click Integrations, then MCP server.
The Integrations panel with the MCP server card

The Integrations panel

The dialog shows the address of this project’s server and a tab for each client: Claude Code, Codex, Cursor, VS Code and Gemini CLI.
The MCP server dialog with the address, a tab for each client and the command for Claude Code

The MCP server dialog

2

Create a token

Click Go to settings. Your account settings open in a new tab. Under Git integration, click Generate token, or Add another token if you already have one. Click Copy and keep the token somewhere safe, because you only see it once. Then click Close.
The Git authentication token dialog with a Copy button

Your new token

A token you already use for Git integration works too, and so does one token for all your projects.
3

Add the server to your client

Back in the dialog, click the tab of your client and click Copy next to the configuration.The address belongs to one project. To connect another project, add it under another name, because overleaf is taken. For Claude Code, for example, change overleaf in the command to overleaf-lab.

Check the connection

With Claude Code

The server is listed as connected:

With curl

This works whatever your client is. Replace the address and the token, and send the initialize request of the MCP protocol:
The answer names the server, followed by its instructions for clients:
To see the tools, send tools/list with the same command. The answer lists 17 tools.
To call one, send tools/call:

In your account settings

Under Git integration, Last used shows the date for a token the server has received.
The token list, with a date under Last used for the first token and N/A for the second

The first token has been used

If it does not connect

What you see when a client works

Edits appear in an open editor as the client makes them, like a collaborator’s, without reloading. New files and folders appear in the file tree.
The editor showing a line that edit_file added, with no dialog and no reload

A line added by edit_file

edit_file only changes text that appears exactly once. Otherwise the client gets an error, such as oldString not found in main.tex, read_file again or oldString appears 2 times in main.tex, add context, and nothing changes. Replies to comments appear in the review panel under your name, because the token is yours. A comment resolved through the server leaves the panel, and reopening it brings it back.
A comment in the review panel with a reply sent by reply_to_comment

A reply sent by reply_to_comment

compile compiles the project and returns the list of output files. get_output_file_link then gives a link to download the PDF or another output file. The link needs no token and stops working after 5 minutes. For the full list of tools and what each role may do, see Tools and Permissions.

Disconnect a client

Delete the token: see Delete a token. From then on, the server answers 401 to that token. If you also use it for Git, Git stops accepting it too.
Last modified on November 7, 2026