tex-mcp-web

tex-mcp-web

Write a LaTeX paper in the session that did the work, and review it from its rendered PDF, on a desktop, tablet, or phone, while Claude Code or Codex edits the source.

The agent that ran your analysis, wrote your code or worked through your data already holds what the paper has to say. Have it write the paper in a folder you name, and say do tex init: from where it is working, the agent shows the settings it proposes, the port and whether the page opens only from your link among them, and sets the review page up for that folder once you agree. Nothing is carried over to another tool by hand. Comment on as many places as you like, then press Call agent once: the agent takes them all in one turn and answers each from the work it did.

Review from the PDF

Select words in the PDF, or draw a box over part of a figure, and write what should change. Press Call agent, the bell above the comments, when they are ready. The agent edits the source, compiles, and answers in the thread, at times with a wording to apply, which you apply or reject. The keys at the bottom right are the ones pressed.

⭐ If this helps your writing, please give it a star. It helps others find the project.

Quick start

1. Paste this into Claude Code or Codex, and start the agent again once it is done:

   Install tex-mcp-web by following https://raw.githubusercontent.com/MiiKiyoshi/tex-mcp-web/main/INSTALL.md

The agent checks for Python 3.10 or newer and latexmk, shows where it will install and which agents it will register with, and installs once you agree.

1. Start the agent in the paper's folder, or stay where the work is with the paper in a folder of its own, and say do tex init. It finds the main .tex file and a free port, shows you the settings, and writes .tex-mcp-web.yaml once you agree.

1. Open http://localhost: . On a machine other people log in to, say yes to the page token at do tex init, and open the link tex-mcp-web link prints once in each browser. The agent acts when you press Call agent. With the plugin the install adds, a Claude Code session started in the paper's folder waits for that press by itself. In Codex, or in an older Claude Code that does not support plugin monitors, say do tex listen first, and again after the agent restarts.

Point at what words cannot

For a figure, a table or a page's layout, take the box tool beside pan and pointer in the PDF's toolbar, draw a box over it, and say what is wrong. The agent works from the box as from any comment.

Answer your co-authors' Overleaf comments, with the agent

Press Connect Overleaf in the top bar and paste the project's link. Its comment threads come into a tab of their own, Comments with a leaf, beside the comments you write here. In a thread you talk with the agent, which drafts the reply for Overleaf under it, and you send that reply once it reads right. Each tab opens on to do, what is not done yet: a comment the agent has yet to answer, a suggestion to apply, a reply to send, a suggested edit to accept. The number on the tab counts them, and once it is gone, nothing is left.

Your talk with the agent stays on the page, in the thread between your co-authors' messages, so the whole exchange reads in order. Overleaf gets only the replies you send.

Keeping the paper's files in step with Overleaf, by git, by hand or live, is in Working with Overleaf.

Raise a point with your co-authors on Overleaf

Press the leaf beside + Comment in the editor's bar, select the words in the source, as Overleaf puts a thread on source words, and tell the agent what to say, as roughly as you like. It drafts the thread's first message, worded for your co-authors, and you send it. It opens on Overleaf on those words, and your note stays here. Asked in any thread, the agent drafts a new thread of its own the same way.

Accept or reject your co-authors' suggested edits

Edits your co-authors make on Overleaf with track changes on come in as suggested edits, each a card of what went and what came, and the editor marks them in the source. Accept and Reject, or aa and dd, act on Overleaf for everyone in the project.

Go through the comments by keyboard

The comment list goes by keys, as a notebook's cells do, and the editor has Vim keys. A ring marks the comment the keys act on, and the list moves under it, so the eye stays put. K goes between a comment and its words in the source, both ways.

Keys that change the file, post to Overleaf or delete are pressed twice. Once you move by keys, the ringed comment's buttons show their letters. Every key, and the editor's Vim keys, are in Reviewing in detail.

Review on a tablet or phone

The page is served where the agent runs. From a phone, forward its port over SSH from that machine, with Termux on Android or Termius on iOS, then open http://localhost: in the phone's browser:

ssh -L <port>:localhost:<port> <the machine the agent runs on>

In Termius the same forward is a Local rule in its Port Forwarding screen. With the page token on, open the link tex-mcp-web link prints on that machine instead, once.

Writes by your rules, in your field's terms

Rules told to an agent in conversation do not last. After its context is compacted a few times it writes as if never told, and what Claude Code remembers for one paper's folder does not reach the next paper in the same field. Kept in files, your writing rules and your field's terms serve every paper that names them, and in Claude Code the agent cannot use tex-mcp's tools until it has read them, again after every compaction (Codex does not hold the tools back like this yet).

Write the rules you hold a paper to in a GUIDELINE.md, in a folder of its own under ~/.config/tex-mcp-web/guidelines/, and set guideline to the folder's name. A guideline can build on another, so the rules for every paper and those of one field stay apart:

~/.config/tex-mcp-web/guidelines/

├── plain-writing/GUIDELINE.md rules for every paper └── my-field/GUIDELINE.md a field's own, opening with the lines below

---

extends: plain-writing

---

With guideline: my-field, the agent reads plain-writing first and my-field after it.

Left alone, an agent also describes a concept in words of its own where the papers of your field use one term. Convert the papers yours builds on to Markdown with marker, keep them in one folder, and set references to it.

Configuration

do tex init writes .tex-mcp-web.yaml at the paper's root:

main: main.tex

watch:

• '*.tex'
• '*.bib'

ignore:

• '*_backup.tex'

compiler: auto port: