[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Overleaf MCP server: Let your AI agent fix your LaTeX and answer comments. > Overleaf's only public API, Open in Overleaf, sends LaTeX in to create a new project. Existing projects are reached through Git on paid plans. There is no official MCP server (checked 6 Nov 2026). Cotlet runs 15 Overleaf tools hosted, over MCP for agents and REST for scripts. Connect your Overleaf projects to your AI agent. It compiles, fixes errors, replies to co-author comments and reviews tracked changes while you write. Nothing to install and no API key from Overleaf. - Free 7-day trial, no card - Not affiliated with Overleaf - Page: https://cotlet.dev/integrations/overleaf-api-mcp-server ## What can your AI agent do in Overleaf? - Fix LaTeX compile errors - Answer co-author comments - Accept typo fixes from tracked changes - See edits since the last labeled version - Tag old projects - Invite reviewers and co-authors ## Does Overleaf have an MCP server or an API? - Open in Overleaf takes a link or a form and opens a new project. It reads nothing back and changes no existing project. - Git integration is a premium feature on Overleaf Cloud and follows the project owner's subscription. Overleaf's docs say pushes can lose or displace comments and tracked changes. - Zapier has no Overleaf app and n8n has no Overleaf integration page (both checked 6 Nov 2026). | What you need | Open in Overleaf | Git integration | Cotlet | |---|---|---|---| | List your projects and tags | No | No | Yes | | Read and edit project files | No | Paid plans, by push | Yes, in the editor | | Compile and read the errors | No | No | Yes | | Comments and tracked changes | No | Pushes can drop them | Yes, they stay in place | | Invite collaborators | No | No | Yes, after your OK | | Works on the free Overleaf plan | Yes | Paid plans only | Yes | Checked 6 Nov 2026. Sources: [Overleaf: Open in Overleaf API](https://www.overleaf.com/devs), [Overleaf Docs: Git integration](https://docs.overleaf.com/integrations-and-add-ons/git-integration-and-github-synchronization/git-integration), [Overleaf: plans and pricing](https://www.overleaf.com/user/subscription/plans), [Zapier: Overleaf page (404)](https://zapier.com/apps/overleaf/integrations) ## How does Cotlet connect to Overleaf? 1. **Sign in to Overleaf.** Use your own account in its Cloud Browser. 2. **Connect your AI agent.** Paste one address into your agent. 3. **Ask in plain words.** Fix my errors, answer my comments. We never keep your Overleaf password, and edits, replies and invites wait for your OK before anyone sees them. ## How to connect Overleaf to your AI agent 1. **Enable Overleaf for agents.** Sign up, log in to Overleaf in its Cloud Browser, then press Enable for agents. 2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One shared address, `https://cotlet.dev/mcp/v1`, also carries Overleaf next to your other apps. If you enable Overleaf after connecting, refresh the connector so the new tools show up. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-overleaf \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-overleaf": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-overleaf] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: overleaf_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: overleaf_write ``` ## All 15 Overleaf MCP tools ### Projects and files Owned and shared projects both appear, with your role. Only text files can be read; images are listed with their size. - **List projects** (`list_projects`, read): List the projects in the account's Overleaf dashboard. - **Get project** (`get_project`, read): Get the settings and sharing of one project. - **List files** (`list_files`, read): List the files and folders of a project. - **Read file** (`read_file`, read): Read the text of one file in a project. - **Edit file** (`edit_file`, write, asks first): Replace a piece of text in one project file. - **Tag project** (`tag_project`, write): Add a tag to a project, or remove it. ### Compile Uses the main document and compiler set in the project. A free account has a 10 second compile limit, paid plans 240 seconds. - **Compile project** (`compile_project`, write): Recompile a project and return the result. ### Comments, tracked changes and history Track changes and full history need a premium plan on the project owner's account. On a free project, history shows the last 24 hours and labeled versions. - **List comments** (`list_comments`, read): List the comment threads of a project. - **Add comment** (`add_comment`, write, asks first): Add a comment on a piece of text in a project file. - **Reply to comment** (`reply_to_comment`, write, asks first): Reply in an existing comment thread. - **Resolve comment** (`resolve_comment`, write, asks first): Mark a comment thread as resolved. - **List tracked changes** (`list_tracked_changes`, read): List the tracked changes waiting for review in a project. - **Accept or reject tracked change** (`review_tracked_change`, write, asks first): Accept or reject one tracked change. - **List history versions** (`list_history_versions`, read): List the saved versions and recent edits of a project from its History. ### Sharing The number of Editors and Reviewers you can invite follows the project owner's plan. A free plan allows 1; Viewers are unlimited. - **Invite collaborator** (`invite_collaborator`, write, asks first): Invite a person to a project by email. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/overleaf-api-mcp-server#tools ## Who can see my Overleaf session, and how do I revoke it? - **What we store.** Your logged-in Overleaf profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 15 Overleaf tools. Never the cookie. - **What the session sees.** Your projects, files, comments and the people you share with. - **What no tool touches.** Billing, plan, password and deleting a project. - **How you sign in.** Email, Google, ORCID, IEEE or SSO. You do it, we never type a password. - **How to cut access.** Disable for agents or reset the browser in the console. Your Overleaf account is untouched. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet. ## What happens when Overleaf changes? - **12 h** between tests of the Overleaf tools - **$0** for a call to an Overleaf tool paused for repair When Overleaf moves a button or renames a field, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the context.** Lists the open comments and the lines they point to. 2. **Changes the text.** Replaces one exact piece of text. It stops if the text appears twice. 3. **Waits for your OK.** The edit or reply shows in your Cotlet console first. 4. **Compiles and reports.** Status, and every error with its file and line. | Action | Undo | |---|---| | Edit a file | Restore the earlier version in Overleaf History (full history on paid plans, the last 24 hours on Free) | | Add or reply to a comment | Edit or delete it in the review panel | | Resolve a comment | The thread moves to the resolved list in the review panel | | Accept or reject a tracked change | Restore the earlier version in History | | Invite a collaborator | Revoke the pending invite under Manage access; the email is already out | | Tag a project | Call the tool again with remove set | 6 of 15 tools ask first: every edit, comment, reply, resolve, tracked change decision and invite, because co-authors see them. Reads, compiles and private tags reach nobody, so they run at once. Switch the wait off per tool for a scheduled run. > Your role in the project decides what Overleaf allows. A Reviewer's edits are tracked, as in the editor. MCP call: ``` { "name": "add_comment", "arguments": { "project_id": "66f1a2b3c4d5e6f708192a3b", "file_path": "sections/intro.tex", "selected_text": "sparse attention show large gains", "body": "Subject and verb do not agree. Also, name the datasets where the gains were measured." } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/overleaf/projects/66f1a2b3c4d5e6f708192a3b/comments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"file_path":"sections/intro.tex","selected_text":"sparse attention show large gains","body":"Subject and verb do not agree. Also, name the datasets where the gains were measured."}' ``` Tool output: ``` { "thread_id": "66fa01b2c3d4e5f607182931", "file_path": "sections/intro.tex", "line": 2, "resolved": false } ``` Scripts and cron jobs reach the same tools over REST, with the same key and price. A call that fails costs nothing. The tools table lists the REST path of each tool. ## How much does the Overleaf MCP server cost? **About $18 a month** for a researcher with a thesis and a paper under review, 3,020 credits. Your Overleaf plan is billed by Overleaf as before. | Job | Calls | Credits | |---|---|---| | Fix compile errors, 3 per draft | 8 × 6 | 480 | | Work through a round of 8 comments | 21 × 3 | 630 | | Review a supervisor's tracked changes | 7 × 3 | 210 | | Check what changed since the last labeled version | 1 × 4 | 40 | | Tag finished projects | 10 × 1 | 100 | | Invite co-authors to a new project | 3 × 2 | 60 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,020 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on Overleaf's free plan too The month is our example, not an Overleaf figure: Overleaf publishes no usage numbers for a typical account. Each fix, reply or tracked change is a read and a write, so a round of 8 comments takes about 21 calls. Overleaf plans, checked 6 Nov 2026: Free $0, Standard $25 a month or $199 a year, Pro $45 a month or $399 a year. Dollars at the $29 pack rate. ## Overleaf MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [mjyoo2/OverleafMCP](https://github.com/mjyoo2/OverleafMCP) | MCP server that reads projects, parses LaTeX structure and pushes section edits through Git. 342 stars, MIT, last commit 3 May 2026. | Runs on your computer and needs Git integration, a paid Overleaf feature. | | [aloth/olcli](https://github.com/aloth/olcli) | Command line tool to pull, push, sync and compile, with an MCP server. 243 stars, MIT, last commit 2 Nov 2026. | You install and run it yourself. | | [lonetis/claudeleaf](https://github.com/lonetis/claudeleaf) | SDK, CLI and MCP server that edits in the Overleaf web editor in real time. 40 stars, MIT, last commit 20 Oct 2026. | Runs on your computer. | | [DanielHou315/overleaf-mcp-rt](https://github.com/DanielHou315/overleaf-mcp-rt) | Real-time MCP server for overleaf.com and self-hosted Overleaf. 13 stars, AGPL-3.0, last commit 20 Sep 2026. | Runs on your computer. | | Overleaf AI Assistant | Built into the editor: chat with your document and LaTeX help. 5 AI uses a day on Free and Student, 10 on Standard, Max on Pro. | Works inside the Overleaf editor only, not from your own agent. | | [Open in Overleaf](https://www.overleaf.com/devs) and Git integration | Overleaf's own routes: one creates a new project, the other syncs files on paid plans. | No compile, comments, tracked changes or invites. | We found no hosted Overleaf MCP server besides ours. A community server is free and fine on your own laptop. Cotlet adds hosting around the clock, use from ChatGPT and your phone, and one account for your other apps. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Overleaf tools. ## Overleaf MCP server: questions ### How do I connect Overleaf to ChatGPT or Claude? Sign up at cotlet.dev, log in to Overleaf once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Overleaf account through Cotlet, in their phone apps too. ### What can ChatGPT do in Overleaf? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Overleaf: fix LaTeX compile errors; work through co-author comments; review tracked changes before submission. You ask in plain words, and anything that reaches other people waits for your OK first. ### How do I get access? Create a free account at https://cotlet.dev, open Overleaf under Integrations in the console and log in to Overleaf in its Cloud Browser. The trial starts with your first app, no card asked. ### Do I need a paid Overleaf plan? No for projects, files, comments, compiles, tags and invites. Track changes needs a premium plan on the project owner's account, and full project history does too: a free project shows the last 24 hours and labeled versions (Overleaf Docs: Premium features, History and versioning). A free plan also allows 1 Editor or Reviewer collaborator per project. ### Is this the same as Overleaf's Git integration? No. Git integration is a premium Cloud feature that clones and pushes files with no branches or tags. It cannot compile, comment or invite. Overleaf also warns that pushes can drop or displace tracked changes and comments (Overleaf Docs: Git integration). Cotlet works in the editor, so comments and tracked changes stay in place. ### Does Overleaf have webhooks? Overleaf documents none (checked 6 Nov 2026), so nothing tells an agent that a co-author commented. Run your agent on a schedule instead, for example a weekly list_comments pass. ### Can the agent edit a project that was shared with me? It can do what your role allows. As a Viewer it can read and compile only. As a Reviewer its edits are tracked, as they would be in the editor. As an Editor it can change files. ### Does it work on the free Overleaf plan? Yes. Cotlet works in your own account on any plan. Overleaf's limits stay: a 10 second compile limit, 1 collaborator per project, no track changes and 24 hours of history on a free project. ### Is the MCP server different from the REST API? Only the door is different. Both expose the same 15 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with Overleaf? No. Cotlet is independent and not affiliated with Overleaf. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.