Overleaf MCP vs PaperDock
A side-by-side look at the Overleaf MCP and PaperDock MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Overleaf MCPDeveloper Tools · Local subprocess (stdio)MCP server that lets AI assistants read Overleaf projects, parse LaTeX document structure, and push section-level edits back via Git.57GoodAuth: api key requiredP
PaperDockDeveloper ToolsCreate, edit, and review LaTeX with AI agents in PaperDock, an independent alternative to Overleaf.38FairAuth: not declaredVerdict: choose Overleaf MCP for developer tools work as a local process; choose PaperDock for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Overleaf MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OVERLEAF_PROJECT_ID, OVERLEAF_GIT_TOKEN, OVERLEAF_GIT_TOKEN_FILE, OVERLEAF_PROJECT_NAME, OVERLEAF_PROJECTS_CONFIG. - You want tools like
list_projects, list_files, read_file.
PChoose PaperDock when
- You need dedicated capabilities in the Developer Tools domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Overleaf MCP | P PaperDock |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | OVERLEAF_PROJECT_IDOVERLEAF_GIT_TOKENOVERLEAF_GIT_TOKEN_FILEOVERLEAF_PROJECT_NAMEOVERLEAF_PROJECTS_CONFIG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 326 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Overleaf MCP | View PaperDock |
Tools & capabilities
Overleaf MCP tools 8
list_projectsList all configured projects.list_filesList files in a project (default: .tex files).read_fileRead a specific file from the project.get_sectionsGet all sections from a LaTeX file.get_section_contentGet content of a specific section.status_summaryGet a comprehensive project status summary.write_fileWrite the full content of a file to the project.write_sectionWrite the content of a specific section to the project.
PaperDock tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Overleaf MCP
{
"mcpServers": {
"mjyoo2-overleaf-mcp": {
"command": "npx",
"args": [
"-y",
"@mjyoo2/overleaf-mcp"
],
"env": {
"OVERLEAF_PROJECT_ID": "YOUR_OVERLEAF_PROJECT_ID_HERE",
"OVERLEAF_GIT_TOKEN": "YOUR_OVERLEAF_GIT_TOKEN_HERE",
"OVERLEAF_GIT_TOKEN_FILE": "YOUR_OVERLEAF_GIT_TOKEN_FILE_HERE",
"OVERLEAF_PROJECT_NAME": "YOUR_OVERLEAF_PROJECT_NAME_HERE",
"OVERLEAF_PROJECTS_CONFIG": "YOUR_OVERLEAF_PROJECTS_CONFIG_HERE"
}
}
}
}
PaperDock
No confirmed install command for PaperDock yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Overleaf MCP is categorized under Developer Tools and uses a local stdio subprocess. PaperDock belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Overleaf MCP for developer tools work and PaperDock for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. PaperDock has no confirmed install command yet — follow its own setup instructions.
Overleaf MCP has no declared pricing — check the project's own site. Auth: api key required. PaperDock has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mjyoo2-overleaf-mcp and paperdock as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Overleaf MCP has a quality signal of 57/100 (Good) with 0 views, 0 installs and 326 GitHub stars. PaperDock has 38/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.