get_section_content
Get content of a specific section
LABSCO SUMMARY
Section-level writes mean a co-author's paragraph is not collateral damage.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — npx -y @mjyoo2/overleaf-mcp, then supply credentials
USE CASES
01
Rewriting one section of a paper
List the sections by title, read the one being revised, and write it back on its own — the surrounding sections are untouched, and the commit message travels with the change.
02
Getting oriented in a co-authored project
See which projects the server is configured for, list the files in one filtered to the extension you care about, and read the project status before changing anything.
03
Adding a file the paper does not have yet
Read an existing file to match its conventions, then write the new one with a commit message that explains it in the project history.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_sections
Get all sections from a LaTeX file
list_files
List files in an Overleaf project
list_projects
List all configured Overleaf projects
read_file
Read a file from an Overleaf project
status_summary
Get a comprehensive project status summary
write_file
Write content to a file in an Overleaf project and push to Overleaf
write_section
Replace 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.
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected.
Requires
- npx on PATH
- OVERLEAF_PROJECT_ID in your environment
- OVERLEAF_GIT_TOKEN in your environment
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @mjyoo2/overleaf-mcpMCP Clients
Claude Desktop — macOS / Linux
CLAUDE DESKTOP — MACOS / LINUX · JSON
{
"mcpServers": {
"overleaf": {
"command": "npx",
"args": [
"-y",
"@mjyoo2/overleaf-mcp"
],
"env": {
"OVERLEAF_PROJECT_ID": "<YOUR_OVERLEAF_PROJECT_ID>",
"OVERLEAF_GIT_TOKEN": "<YOUR_OVERLEAF_GIT_TOKEN>"
}
}
}
}Claude Desktop — Windows
CLAUDE DESKTOP — WINDOWS · JSON
{
"mcpServers": {
"overleaf": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@mjyoo2/overleaf-mcp"
],
"env": {
"OVERLEAF_PROJECT_ID": "<YOUR_OVERLEAF_PROJECT_ID>",
"OVERLEAF_GIT_TOKEN": "<YOUR_OVERLEAF_GIT_TOKEN>"
}
}
}
}
