Kwork vs Overleaf MCP
A side-by-side look at the Kwork and Overleaf MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kwork for developer tools work as a local process; choose Overleaf MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kwork when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KWORK_WRITES, KWORK_EXPECTED_USER_ID, KWORK_SITE. - You want tools like
account_status, get_connects, discover_projects.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | KWORK_WRITESKWORK_EXPECTED_USER_IDKWORK_SITE | OVERLEAF_PROJECT_IDOVERLEAF_GIT_TOKENOVERLEAF_GIT_TOKEN_FILEOVERLEAF_PROJECT_NAMEOVERLEAF_PROJECTS_CONFIG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 329 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 8 |
| Full listing | View Kwork | View Overleaf MCP |
Tools & capabilities
Kwork tools 4
account_statusФактический account ID, binding, готовность writes и `unresolved_write_idsget_connectsАктивные и общие коннектыdiscover_projectsfavorites`, `all` или `category_ids`, фильтры и opaque cursorlist_notificationsПолные группы уведомлений
Overleaf MCP tools 8
list_projectsList all configured Overleaf projectslist_filesList files in an Overleaf projectread_fileRead a file from an Overleaf projectget_sectionsGet all sections from a LaTeX fileget_section_contentGet content of a specific sectionstatus_summaryGet a comprehensive project status summarywrite_fileWrite content to a file in an Overleaf project and push to Overleafwrite_sectionReplace a single section in a LaTeX file and push to Overleaf. Safer than write_file for targeted edits — only the named section is replaced, leaving the rest of the file untouched.
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.
Kwork
{
"mcpServers": {
"kwork": {
"command": "uvx",
"args": [
"kwork-mcp@1.5.2"
],
"env": {
"KWORK_WRITES": "YOUR_KWORK_WRITES_HERE",
"KWORK_EXPECTED_USER_ID": "YOUR_KWORK_EXPECTED_USER_ID_HERE",
"KWORK_SITE": "YOUR_KWORK_SITE_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Kwork is categorized under Developer Tools and uses a local stdio subprocess. Overleaf MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Kwork for developer tools work and Overleaf MCP 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.
Kwork has no declared pricing — check the project's own site. Overleaf MCP has no declared pricing — check the project's own site. Auth: api key required. 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 kwork and mjyoo2-overleaf-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kwork has a quality signal of 52/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Overleaf MCP has 65/100 (Great) with 0 views, 0 installs and 329 GitHub stars.