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.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 14/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 26/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 LaTeX Look。按照 https://mcp.popnx.com/i/fangchenghao-latex-look.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server LaTeX Look,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "latex-look": { "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 LaTeX Look 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"latex-look": {
"command": "npx",
"args": [
"-y",
"@fffangchenghao/dsh-latex-look",
"mcp"
]
}
}
}用 LaTeX Look 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 LaTeX Look,或回答中出现 LaTeX Look 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 LaTeX Look
LaTeX Look 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 LaTeX Look 的应用
B · 旅行、地图与天气 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server LaTeX Look,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user latex-look -- npx -y @fffangchenghao/dsh-latex-look mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 LaTeX Look 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user latex-look -- npx -y @fffangchenghao/dsh-latex-look mcp应能看到 LaTeX Look 在列表中并显示已连接
用 LaTeX Look 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 LaTeX Look,或回答中出现 LaTeX Look 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server LaTeX Look,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "latex-look": { "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 LaTeX Look 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 LaTeX Look 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 LaTeX Look,或回答中出现 LaTeX Look 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server LaTeX Look,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "latex-look": { "type": "stdio", "command": "npx", "args": [ "-y", "@fffangchenghao/dsh-latex-look", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 LaTeX Look 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 LaTeX Look 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 LaTeX Look,或回答中出现 LaTeX Look 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
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"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 fangchenghao 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/fangchenghao-latex-look)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.4.3)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Mu, Award Travel Finder, Killbottleneck, Whimsical, HasData Google Maps
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 LaTeX Look | Mu | Award Travel Finder | Killbottleneck | Whimsical | HasData Google Maps | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 是 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 3/3 | 4/4 | 5/5 |
| 许可证 | MIT | AGPL-3.0 | MIT | MIT | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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