The section tools read a paper the way its authors think about it, and write_section replaces one named section rather than the file, so an agent rewriting the introduction cannot quietly take the results with it. Every write carries a commit message, which leaves a history in Overleaf that a human can walk back. Projects are configured into the server rather than discovered, so adding a new paper is a configuration change and not a call.
A server over an Overleaf project through its Git access, with LaTeX-aware reads — sections parsed out of a file rather than only whole files.
- Files listed per project and filterable by extension, then read in full
- Sections parsed out of a LaTeX file, listed by title and fetched one at a time
- A section-level write that replaces one named section and leaves the rest of the file untouched
- Whole-file writes for changes that are not sectional, each carrying its own commit message on the way to Overleaf
- A project status summary, and a listing of the projects the server has been configured with
OVERLEAF_PROJECT_ID and OVERLEAF_GIT_TOKEN for the project you intend to edit; writes go out over Overleaf's Git access, so the token has to be one that can push. MIT.
One command plus a key — npx -y @mjyoo2/overleaf-mcp, then supply credentials