Plugin directory / Developer / dsh-overleaf
dsh-overleaf
Verified · install-tested on dsh fly233338
What it does
Connect Overleaf projects to DeepSeek Harness (DSH) through OverleafMCP and MCP tools.
Works — verified, early-stage project
Connect Overleaf projects to DeepSeek Harness (DSH) through OverleafMCP and MCP tools. It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-overleaf
Connect multiple Overleaf projects to DeepSeek Harness (DSH) through @fly233338/overleaf-mcp.
dsh-overleaf installs @fly233338/overleaf-mcp as an npm dependency, starts it through MCP stdio, and exposes its tools to DSH. The OverleafMCP source is not copied into this project.
Features
Browse and read files from multiple Overleaf projects, inspect document sections and section content, write files or sections back to Overleaf through Git, and use the DSH MCP Client provided by the host. Based on my experience, it is especially useful in the following scenarios: understanding an entire LaTeX project, automatically fixing LaTeX compilation errors, and unifying terminology and symbols throughout the document.
Requirements
- DSH
0.1.0-rc.5or a compatible release. - Node.js
22.19.0or newer. - An Overleaf Git integration token.
Install
If the DSH CLI is installed and available on PATH:
dsh plugin --profile web add dsh-overleaf
dsh web
From a DSH source checkout:
cd /path/to/deepseek-harness
pnpm install
pnpm run build
pnpm dsh plugin --profile web add /path/to/dsh-overleaf
pnpm dsh web
The npm installation command becomes available after this package is published.
Configure
The plugin stores dsh-overleaf.config.json under $DSH_HOME/dsh-overleaf/. If DSH_HOME is not set, it uses ~/.dsh/dsh-overleaf/. The directory and file are created on startup when missing. Fill in one shared token and one project ID per line:
{
"gitToken": "your-overleaf-git-token",
"projectIds": [
"project-id-a",
"project-id-b"
]
}
Get project IDs from the <id> in the Overleaf project URL. Create the Git token under Overleaf Account Settings → Git Integration.
Restart DSH after editing the file. The plugin reads it once at startup and generates the internal .dsh-overleaf.projects.json OverleafMCP project configuration in the same directory. Do not edit the generated file.
The plugin does not read .env and does not require Overleaf environment variables.
Use with the model
Tell the model which project to handle:
Please work on Overleaf project project-id-a and read its main.tex.
The model first calls mcp__overleaf__list_projects, then passes the selected ID as projectName to subsequent Overleaf tools. Write operations require an explicit commitMessage and push a Git commit to Overleaf.
Keep the token out of public source repositories and published package contents.
Scope
The current version supports multiple Overleaf projects through one MCP tool group. It does not compile documents, review PDFs, or automate a browser.
Links
- Project repository
- @fly233338/overleaf-mcp (npm)
- DSH plugin guide
- insert:
- id: dsh-overleaf
name: dsh-overleaf
- id: dsh-overleaf
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-overleaf for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-overleaf Headless (CLI) profile:
dsh plugin --profile headless add dsh-overleaf Package
npm: dsh-overleaf · version — · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.