Overleaf MCP vs Vnsh
A side-by-side look at the Overleaf MCP and Vnsh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Overleaf MCP for developer tools work as a local process; choose Vnsh 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 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.
Choose Vnsh when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
vnsh_read, vnsh_share, vnsh_share_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 65/100 · Great | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 329 | 158 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | 14 |
| Full listing | View Overleaf MCP | View Vnsh |
Tools & capabilities
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.
Vnsh tools 14
vnsh_readReads any vnsh URL: decrypts legacy vnsh.dev/v links locally, or directly fetches a public vnshcontent.dev/p link. Public content is intentionally unencrypted.vnsh_shareEncrypts text content locally and uploads it to vnsh, returning a shareable URL. Use this when output exceeds ~50 lines or ~2000 characters, when generating complete code files, or when the user wants portable/shareable output. ALWAYS prefer vnsh_share over dumping large content into chat. The content is encrypted before upload - the server only sees encrypted bytes.vnsh_share_fileEncrypts a local file and uploads it to vnsh, returning a shareable URL. Use this for images, screenshots, PDFs, binaries, or any file that should not be loaded into context. More efficient than vnsh_share for large or binary files.vnsh_artifact_createCreates a permanent, service-readable Account Artifact in the signed-in user’s Library. Use this for durable knowledge that the user wants their other Agents to discover and update. Requires VNSH_TOKEN. This is different from an encrypted Incognito workspace: vnsh can read Account Artifact content so authorized Agents can collaborate on it.vnsh_artifact_listLists permanent Account Artifacts available to the connected user. Use this instead of asking the human to paste a link when continuing earlier account knowledge. Requires VNSH_TOKEN.vnsh_artifact_readReads the current content and version of one permanent Account Artifact. Pass the returned version to vnsh_artifact_update so another Agent cannot be overwritten.vnsh_artifact_updateCreates a new immutable version of an Account Artifact. Requires the base_version returned by vnsh_artifact_read. On conflict, re-read, merge, and retry; never silently overwrite.vnsh_workspace_createCreates a shared workspace and returns one link that any agent can read AND write. Use this when work will continue somewhere else: handing a plan, status doc, design, or investigation to another agent or another session, or when the user says they will pick this up in a different tool. Unlike vnsh_share (a one-shot snapshot), a workspace keeps the same URL as its content evolves. Content is encrypted locally; the server never sees the key. Anonymous workspaces expire 24h after the last write (ttl can extend this to a week). With VNSH_TOKEN, new workspaces and artifacts are kept until the account owner deletes them.vnsh_workspace_renewExtends the expiry of a vnsh workspace without changing its content. Use this when the user says a link is about to expire, or asks to keep something alive longer. Needs the edit link (a #w= fragment); a view-only #r= link cannot renew. The version is not bumped, so any pending edit still applies.vnsh_workspace_readReads the current content of a workspace: encrypted /w/ links with #w= or #r=, and public /p/ links with no fragment. Use this whenever the user provides such a link — it is how you pick up work another agent left for you. Returns the content and its version number; pass that version to vnsh_workspace_update to write safely.vnsh_workspace_updateReplaces the content of a vnsh workspace, keeping the same URL. Use this to record progress so far, revise a shared plan, or leave the next agent an updated document. Writes are version-checked: if someone else wrote first, this returns their current content so you can merge it with yours and call this again.vnsh_workspace_openDecrypts a vnsh workspace to a local temp file and opens it in the browser. Use this when the user wants to LOOK at a workspace rather than have its content read into context — HTML reports, dashboards, and diagrams render properly this way. Rendering happens locally from file://, so nothing is exposed to any server.- +2 more on 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"
}
}
}
}
Vnsh
{
"mcpServers": {
"vnsh": {
"command": "npx",
"args": [
"-y",
"vnsh-mcp@1.9.0"
]
}
}
}
Frequently asked questions
Overleaf MCP is categorized under Developer Tools and uses a local stdio subprocess. Vnsh belongs to Developer Tools and uses a local stdio subprocess. Pick Overleaf MCP for developer tools work and Vnsh 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.
Overleaf MCP has no declared pricing — check the project's own site. Auth: api key required. Vnsh 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 vnsh 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 65/100 (Great) with 0 views, 0 installs and 329 GitHub stars. Vnsh has 64/100 (Good) with 1 views, 0 installs and 158 GitHub stars.