MIT-licensed DSH plugin that exposes OverleafMCP over MCP stdio, letting DeepSeek Harness read and Git-commit edits across multiple Overleaf LaTeX projects configured with one token.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-14
License
MIT
01What can it help you accomplish?
Understand a whole LaTeX project inside DeepSeek Harness instead of pasting fragments
The model lists Overleaf projects with `mcp__overleaf__list_projects`, then reads files and inspects sections and section content through the OverleafMCP tools
LaTeX authors who want the agent to see the real project structure before editing
Fix LaTeX compilation errors and unify terminology and symbols across the document
Files or sections written back to Overleaf through Git, each write carrying an explicit `commitMessage` and pushing a commit
Paper writers who want the agent to repair and normalize a long document rather than suggest patches by hand
Work across several Overleaf projects from one DSH session
One MCP tool group covering every project ID listed in `dsh-overleaf.config.json`
People maintaining more than one Overleaf paper or report at the same time
02How to install into DeepSeek Harness
Prerequisites
- DSH `0.1.0-rc.5` or `0.2.x` (verified against `0.2.0-rc.2`)
- Node.js `22.19.0` or newer
- An Overleaf Git integration token
Installation steps
- 01
If the DSH CLI is on `PATH`: `dsh plugin --profile web add dsh-overleaf`, then `dsh web`
$ dsh plugin --profile web add dsh-overleaf
- 02
From a DSH source checkout: `pnpm install`, `pnpm run build`, `pnpm dsh plugin --profile web add /path/to/dsh-overleaf`, `pnpm dsh web`
- 03
Create `dsh-overleaf.config.json` under `$DSH_HOME/dsh-overleaf/` (or `~/.dsh/dsh-overleaf/`) with `gitToken` and the `projectIds` list, then restart DSH
Verify the integration
- Tell the model which project to work on — it first calls `mcp__overleaf__list_projects`, which confirms the OverleafMCP tools are wired into DSH
03DSH integration and capability boundaries
A DSH plugin that installs `@fly233338/overleaf-mcp` as a dependency, starts it over MCP stdio and exposes its tools to DSH's MCP Client
Project listing and file reading across Overleaf projects
Overleaf project IDs configured in `dsh-overleaf.config.json`→project list from `mcp__overleaf__list_projects`, file contents, and document sections with their content
Writing files and sections back through Overleaf Git
a file or section edit plus an explicit `commitMessage`→a Git commit pushed to the Overleaf project
pushes a Git commit to the Overleaf projectGenerated OverleafMCP project configuration
the shared `gitToken` and `projectIds` in `dsh-overleaf.config.json`→an internal `.dsh-overleaf.projects.json` that OverleafMCP reads, written in the same directory
writes and regenerates `.dsh-overleaf.projects.json` next to the user config
04Who is it for? When not to use it?
Good for
- LaTeX authors who want the agent to see the real project structure before editing
- Paper writers who want the agent to repair and normalize a long document rather than suggest patches by hand
- People maintaining more than one Overleaf paper or report at the same time
Not for
- The plugin does not compile documents, review PDFs or automate a browser; it only reads and writes Overleaf project content through the MCP tool group.
- You need an Overleaf Git integration token, and the README warns to keep that token out of public source repositories and published package contents. Configuration is read once at startup, so DSH has to be restarted after editing it.
- The README pins DSH `0.1.0-rc.5` or `0.2.x` (verified against `0.2.0-rc.2`) and Node.js `22.19.0` or newer, and notes the npm install command only works once the package is published.
- Every write needs an explicit `commitMessage` and lands as a Git commit in Overleaf, so edits are real project history rather than a local scratch change.
05Compatibility, maintenance and safety notes
- The plugin does not compile documents, review PDFs or automate a browser; it only reads and writes Overleaf project content through the MCP tool group.
- You need an Overleaf Git integration token, and the README warns to keep that token out of public source repositories and published package contents. Configuration is read once at startup, so DSH has to be restarted after editing it.
- The README pins DSH `0.1.0-rc.5` or `0.2.x` (verified against `0.2.0-rc.2`) and Node.js `22.19.0` or newer, and notes the npm install command only works once the package is published.
- Every write needs an explicit `commitMessage` and lands as a Git commit in Overleaf, so edits are real project history rather than a local scratch change.
MIT · README evidence only, no tagged release, no security audit
06Frequently asked questions
How do I install dsh-overleaf into DeepSeek Harness?
With the DSH CLI on `PATH`, run `dsh plugin --profile web add dsh-overleaf` and then `dsh web`; from a DSH source checkout use `pnpm install`, `pnpm run build`, `pnpm dsh plugin --profile web add /path/to/dsh-overleaf` and `pnpm dsh web`. The README notes the plain npm install command only becomes available once the package is published.
Where does the plugin read the Overleaf token and project IDs?
From `dsh-overleaf.config.json` under `$DSH_HOME/dsh-overleaf/`, or `~/.dsh/dsh-overleaf/` when `DSH_HOME` is unset; the directory and file are created on startup if missing. Put one shared `gitToken` and one project ID per line in `projectIds`, then restart DSH — the plugin reads the file once at startup and generates the internal `.dsh-overleaf.projects.json` that OverleafMCP uses.
How does the model pick which Overleaf project to work on?
You tell it the project, for example "work on Overleaf project project-id-a". The model first calls `mcp__overleaf__list_projects` and then passes the selected ID as `projectName` to the subsequent Overleaf tools, so the same MCP tool group serves every project ID you configured.
What can it not do inside DSH?
The README is explicit: the current version does not compile documents, review PDFs or automate a browser. It also needs DSH `0.1.0-rc.5` or `0.2.x` and Node.js `22.19.0` or newer, and every write operation requires an explicit `commitMessage` and pushes a Git commit to Overleaf.
07Related DSH workflows
rea
by morluto
Reverse engineer anything with agents, from app behavior down to native binaries.
reactive-resume
by reactive-resume
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
next-ai-draw-io
by dayuanjiang
Draw and edit draw.io diagrams by chatting with an AI. Web app, desktop app, and an MCP server for Claude Code, Cursor, Codex and VS Code.
everos
by evermind-ai
One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, tools, and workflows.
08Data and sources
`dsh-overleaf` installs [@fly233338/overleaf-mcp](https://www.npmjs.com/package/@fly233338/overleaf-mcp) as an npm depen…
Browse and read files from multiple Overleaf projects, inspect document sections and section content, write files or sec…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-14. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.