Overleaf and LaTeX,
inside every AI
conversation.
vibeTeX is the everything Overleaf MCP server — a Git bridge, project sync, and LaTeX compile for Claude and any MCP client. Pull, edit, push, build the PDF, and check every reference, without leaving the chat.
MIT-licensed · 26 tools · Local compile · Self-host free
Pull my thesis from Overleaf, compile it, and fix any broken references.
Pulled thesis via the git bridge and compiled with latexmk — PDF built, 0 errors. One cross-reference was dangling: \ref{fig:results} pointed at a figure whose label is actually fig:main-results.
edited chapters/results.tex · line 142
- see Figure \ref{fig:results}
+ see Figure \ref{fig:main-results}
Pushed the fix back to Overleaf. Recompiled clean — every \ref and \cite now resolves.
One command. Any MCP client.
Compile works out of the box. Add your Overleaf git token and a project id for full read / write / history over the official git bridge.
Claude Code
claude mcp add vibetex \ -e OVERLEAF_GIT_TOKEN=your_token \ -e OVERLEAF_PROJECT_ID=your_id \ -- npx -y @oscardvs/vibetex
Cursor / VS Code (mcp.json)
"vibetex": {
"command": "npx",
"args": ["-y","@oscardvs/vibetex"],
"env": { "OVERLEAF_GIT_TOKEN": "…",
"OVERLEAF_PROJECT_ID": "…" }
}claude.ai (hosted, paid)
Add a custom connector → https://mcp.vibetex.dev/mcp
Your paper lives in Overleaf.
Your AI can’t touch it.
You copy a section into chat, paste the suggestion back, switch tabs to compile, hunt the log for the one error, then discover a dangling \ref. vibeTeX closes the loop: your assistant pulls, edits, pushes, compiles, and reference-checks the real project — end to end.
Four capability tiers, auto-detected. Always the most it can do.
vibeTeX degrades gracefully — paid git token, free compile, one-click create, or the experimental free-tier sync. overleaf_whoami reports exactly which tiers are live right now.
Git bridge — the robust core
Full read/write plus commit history over Overleaf’s official git authentication token. Pull, edit, push, diff — your project as a real working copy. Requires a paid Overleaf token.
Local & CLSI compile
Build to PDF and parse the log with latexmk, tectonic (zero-TeXLive), or pdflatex — or point at a self-hosted CLSI. No Overleaf premium needed to compile.
Reference-check that fixes
latex_check_refs cross-validates every \ref, \cite, and \label against your .bib and document — then your AI repairs the dangling ones, with a cited diff.
Open in Overleaf
No account, no auth: turn generated LaTeX into a brand-new Overleaf project in one click (one-way).
Free-tier friendly
An opt-in, experimental session-cookie tier is the only way free Overleaf users get list / pull / push / compile.
26 typed tools · local-first
Discovery, project sync, compile, and quality checks — outline, lint, format, word-count, and BibTeX. Your git token talks only to your own Overleaf, never stored beyond the session.
Read the docsvibeTeX vs. the alternatives
| Capability | vibeTeX | Other Overleaf MCPs | By hand |
|---|---|---|---|
| Official git bridge: read / write / history | Yes | Partial | No |
| Compile to PDF + parse the log | Yes | rare | Yes |
| Cross-reference & citation check | Yes | No | manual |
| Open generated LaTeX in Overleaf | Yes | some | manual |
| Free-tier sync (experimental) | Yes | No | Not applicable |
| No Python — TypeScript, one npx | Yes | varies | Not applicable |
| Open-source (MIT) · self-host free | Yes | varies | Not applicable |
| Pay-once hosted option | Yes | rare | Not applicable |
Self-host free. Hosted, pay once.
Self-hosted
Free
MIT-licensed. Run it yourself, forever.
- · Every feature, no paywall
- · Local-first, your own tokens
- · Self-host the OAuth remote for a team
Hosted
€30/year
pay once · 1-year license — a managed, always-on connector.
- · Zero setup — connect in claude.ai
- · One-time license key, 1-year expiry
- · You keep your data & tokens
Stop tab-switching to ship your paper.
Connect Overleaf and LaTeX to your AI in under a minute. Open-source, local-first, free to self-host.