Mu
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Compile a LaTeX page, see it rendered, map a PDF point back to source, and diff builds.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 14/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 26/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install LaTeX Look. Follow https://mcp.popnx.com/i/fangchenghao-latex-look.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server LaTeX Look for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "latex-look": { "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LaTeX Look tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"latex-look": {
"command": "npx",
"args": [
"-y",
"@fffangchenghao/dsh-latex-look",
"mcp"
]
}
}
}Use LaTeX Look and tell me what you can do for me, then show me one thing✓ If Claude says it is using LaTeX Look or shows a LaTeX Look tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect LaTeX Look yet
LaTeX Look runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect LaTeX Look
B · Others in Travel, maps & weather that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server LaTeX Look for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user latex-look -- npx -y @fffangchenghao/dsh-latex-look mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LaTeX Look tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user latex-look -- npx -y @fffangchenghao/dsh-latex-look mcpYou should see LaTeX Look listed as connected
Use LaTeX Look and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using LaTeX Look or shows a LaTeX Look tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server LaTeX Look for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "latex-look": { "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LaTeX Look tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use LaTeX Look and tell me what you can do for me, then show me one thing✓ If Cursor says it is using LaTeX Look or shows a LaTeX Look tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server LaTeX Look for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "latex-look": { "type": "stdio", "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LaTeX Look tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use LaTeX Look and tell me what you can do for me, then show me one thing✓ If VS Code says it is using LaTeX Look or shows a LaTeX Look tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user latex-look -- npx -y @fffangchenghao/dsh-latex-look mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"latex-look": {
"command": "npx",
"args": [
"-y",
"@fffangchenghao/dsh-latex-look",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"latex-look": {
"command": "npx",
"args": [
"-y",
"@fffangchenghao/dsh-latex-look",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"latex-look": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@fffangchenghao/dsh-latex-look",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @fffangchenghao/dsh-latex-lookBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account fangchenghao, which owns the repo
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/fangchenghao-latex-look)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.4.3) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Mu, Award Travel Finder, Killbottleneck, Whimsical, HasData Google Maps
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.
Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.
| This one LaTeX Look | Mu | Award Travel Finder | Killbottleneck | Whimsical | HasData Google Maps | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | Yes | No | Yes |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 3/3 | 4/4 | 5/5 |
| License | MIT | AGPL-3.0 | MIT | MIT | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
English · 简体中文
*Left: compiles with zero errors. Right: after five sentences a reader could say out loud — "remove the rules around the title", "this table is a grid, make it a booktabs table", "that link runs off the page", "the figure is too wide". Try it yourself in examples/broken-layout.*
A DeepSeek Harness plugin that adds exactly one tool: latex_look.
An agent that only reads .tex source is blind: a document can compile with zero errors and still look wrong. latex_look compiles the document, renders the page as an image, maps any spot on that page back to the exact source line, and diffs what your last edit changed — in a single call.
┌─────────────┐ latex_look ┌──────────────┐
│ agent │ ─────────────► │ pdf → png │ │ (edits .tex)│ │ synctex │ └─────────────┘ ◄───────────── │ pixel diff │ ▲ image + line └──────────────┘ └─────────────── verification ───────────┘
Read the case study: a 215-page LaTeX book, read the way a reader reads it — 163 figures, 129 equations, six classes of defect that compile cleanly.
Rendering, locating, and diffing are the *implementation*. The agent needs one coherent verb — "look at this page" — the same way a person does. latex_look compiles, renders, resolves, and diffs in a single call, so the loop is:
look → diagnose → edit .tex → look again → confirm the change → report
Requires Node ≥ 18, a TeX engine (xelatex/lualatex/pdflatex/latexmk or tectonic), synctex, and ghostscript.
This repository is the bundle: package.json declares dsh.bundle.patch, and cordis.patch.yml inserts one row.
git clone https://github.com/fangchenghao/latex-look
Then install it into the current profile (in the Harness, via the plugin manager):
plugin_manager action: install_bundle target: /absolute/path/to/latex-look
That adds the row latex-look and registers the latex_look tool. Replacing the sources of an already-installed package needs a Harness restart to load a fresh module generation.
Published on npm as @fffangchenghao/dsh-latex-look, so the same row also installs straight from the registry:
plugin_manager action: install_bundle target: @fffangchenghao/dsh-latex-look
Two different facts, and the plugin reports them separately because confusing them is how an update goes missing:
A newer release exists. The registry is asked once a day, in the background; when something newer is published, one line is appended to a tool reply. An offline machine sees nothing at all, and an unreachable registry is never reported as "up to date".
A newer release is already installed. This is the one that silently bites. An updater replaces the package directory while the old code keeps running, so the running code goes on reading its version out of a package.json that was swapped underneath it — it reports the *new* number while executing the *old* code, and everything looks current. The plugin therefore remembers the version it started with, re-reads the disk at most once a minute, and when the two disagree says so:
note: @fffangchenghao/dsh-latex-look 0.4.2 is installed on disk, but this process is
still running 0.4.1 — restart DeepSeek Harness to load it.
The plugin does not update itself. Replacing the files of a running process is the profile's job, not a tool's: an updater plugin already installed in the profile does it, or you do it by hand. When the plugin can tell which profile it was installed into, it prints the exact command — the profile name is read off its own path, because they are called desktop and web and a guess sends you to an install that does nothing:
dsh plugin --profile desktop add @fffangchenghao/dsh-latex-look@latest
core.mjs is not hot-reloaded, so a plugin update takes effect on the next start of the harness, never mid-session.
From a checkout, both questions are available directly:
node bin/latex-look.mjs --version
node bin/latex-look.mjs --check-update
Tagging v* runs the platform and MCP suites on Ubuntu with TeX and Ghostscript installed, verifies the tag matches package.json, and publishes to npm. The full npm test suite is the local gate. The token comes from the NPM_TOKEN repository secret.
The tool gives the agent eyes. SKILL.md gives it the LaTeX knowledge to act on what it sees — a symptom → cause → fix playbook (a rule you want gone is usually \pagestyle/fancyhdr, not a stray \hline). Copy or symlink it into the skills root:
mkdir -p ~/.dsh/skills/latex-look
ln -sf "$PWD/SKILL.md" ~/.dsh/skills/latex-look/SKILL.md
node bin/latex-look.mjs book.tex --page 37
node bin/latex-look.mjs book.tex --text "表3.1" node bin/latex-look.mjs book.tex --page 12 --compare previous --json node bin/latex-look.mjs book.tex --page 1 --audit # what did the last edit break, anywhere?
The CLI runs the same engine as the plugin and needs no Harness, which makes it the fast way to check a change without reloading anything.
The same engine ships as a Model Context Protocol server, so a client that has never heard of DSH can use it. It is the same look() and the same words in the reply — the plugin is the Harness shape, this is the universal one.
{
"mcpServers": { "latex-look": { "command": "npx", "args": ["-y", "@fffangchenghao/dsh-latex-look", "mcp"] } } }
Put that in claude_desktop_config.json (Claude Desktop), ~/.cursor/mcp.json (Cursor), or as a TOML block in ~/.codex/config.toml:
[mcp_servers.latex-look]
command = "npx" args = ["-y", "@fffangchenghao/dsh-latex-look", "mcp"]
It exposes one tool, latex_look, with the same parameters as everywhere else: file, page, text, pointX/pointY, compare, audit, sequence, dpi. Pages come back as image content blocks, so the model sees the page itself.
Requirements are the usual ones — a TeX engine and ghostscript on PATH:
brew install --cask mactex-no-gui ghostscript # macOS
sudo apt install texlive-xetex ghostscript # Debian/Ubuntu winget install MiKTeX.MiKTeX ArtifexSoftware.GhostScript # Windows
On Windows nothing has to be added to PATH: the plugin asks for gswin64c (that is Ghostscript's real name there), and when that is not found it looks in C:\Program Files\gs\gs*\bin, plus the TeX Live, MiKTeX and TinyTeX install directories. If you would rather be explicit, point PATH at C:\Program Files\gs\gs10.05.1\bin and it is used first.
Nothing is uploaded: every call compiles the document that is already on your disk.
Listed in the official MCP Registry as io.github.fangchenghao/latex-look, so clients that search the registry can install it by name, and on awesome-mcp-servers.
Ten suites run on a clean checkout. Integration cases create their own fixtures and compile real documents; unit cases and two CLI option/error probes use controlled inputs or stubs. Expect a few minutes (npm test runs these, in this order):
node test/platform.mjs # win32 branches of PATH/PATHEXT/Ghostscript lookup, on any OS
node test/smoke.mjs # unit level: problem parsing, PPM, raster diff, aux detection node test/scenarios.mjs # 52 end-to-end cases driven through index.js node test/scenarios-deep.mjs # 34 cases: multi-file papers, beamer, twocolumn, images,
node test/cli.mjs # the CLI's own argument handling, through the real binary node test/mcp.mjs # the MCP server on the wire: handshake, schema, real call node test/review-core.mjs # restored timestamps, concurrent renders, snapshots, inputs node test/review-sequence.mjs # complete label scans and TOC pass semantics node test/review-audit.mjs # blank/failed builds must not become clean baselines node test/review-update.mjs # loaded version vs disk, semver precedence
Optional book suites (not part of npm test):
node test/book-scenarios.mjs # 15 cases against a real 208-page book (164 .tex files)
node test/book-tasks.mjs # 18 real editing tasks on the same book (see below) LATEX_LOOK_BOOK=/pristine/copy node test/book-tasks.mjs # point it at an unedited copy
The book suite needs a real book and is skipped unless you point it at one:
LATEX_LOOK_BOOK=/path/to/book node test/book-scenarios.mjs
These two suites matter most, because a real book is root → \input{main} → \input{chap1}, with a custom .sty, 181 figures, a glossary and fancyhdr page furniture.
book-scenarios checks the machinery on that book. book-tasks checks the *requests*: each case is a sentence a user would say, applied to the copy and then verified the way an agent verifies it — look, diff against the previous build, and confirm the change is where the edit acts:
| user says | measured |
|---|---|
| 把页眉那条横线去掉 | 0.09%, bbox y=52 h=1 (a thin band at the top) |
| 页眉的线太细,加粗到 2pt | 0.27%, bbox y=52 h=3 |
| 链接的蓝色去掉 | 0.29%, bbox over the contents page |
| 行距调大一点 | 10.53%, 208 → 248 pages |
| 表格行距加大 | 9.07% |
| chap2 那个总结框太窄,放宽 | 7.39% |
| chap1 那个图太小,放大 | 10.57% |
| chap4 那组图对齐时右边空着 | 8.81% |
| 段落首行不要缩进 | 14.07% |
| 页边距太窄 | 13.32%, 208 → 226 pages |
| 正文字号改成 12pt | 11.63%, 208 → 226 pages |
| 目录只显示到章 | 2.19%, 208 → 207 pages |
Nothing in these cases is asserted about how the change *looks* — that is what the image is for. The assertions are: the build succeeded, a diff exists, and its bounding box is in the region the edit acts on.
Both end-to-end suites stub only @deepseek-ai/dsh-tools (it exists solely inside the Harness) and call the real execute with real arguments, so they exercise the argument handling and the exact text the model reads — not just lib/core.mjs. That matters: several bugs found this way lived only in the formatting layer.
SyncTeX records the page a box was built on. A float that TeX moves to the next page gets the previous page's number, so text: "Version 0.5" used to answer "page 205" for a table that ships on 206 — and page 205 is a different chapter. The tool now checks the PDF's own text layer (gs -sDEVICE=txtwrite, ~0.12 s a page) and looks one and two pages either side; when it overrules SyncTeX it says so.
A compare call writes three images, but the one to show the user is images.sideBySide: the page before on the left, the page after on the right, one PNG. Finding the difference by eye across two separate files is the hardest part of the job for someone who cannot read the source.
Writing a PNG needs no dependency — a signature, IHDR, one zlib IDAT, IEND, and node:zlib supplies the compression. The composite costs about 0.3 s on an A4 page at 140 dpi, and only runs when there is something to compare.
Verifying an edit always co