fly233338/dsh-overleaf

Connect Overleaf projects to DeepSeek Harness (DSH) through OverleafMCP and MCP tools.

Bundle verified MIT JavaScript Unknown
Bundle verified

Listed

7

Docs

Bundle verified

VersionUnknown
LanguageJavaScript
LicenseMIT
View on GitHub

Preview

Preview 1 of 2: fly233338/dsh-overleaf
Preview 2 of 2: fly233338/dsh-overleaf

What it does

Connect multiple Overleaf projects to DSH through OverleafMCP for browsing, analysis, and Git-based file updates.

Best for

  • Authors managing multiple Overleaf projects who want to browse and analyze LaTeX sources from DSH.
  • Document-maintenance workflows such as understanding a full project, fixing source-level compilation errors, or unifying terminology and notation.
  • Teams that want explicit Git commits when writing files or sections back to Overleaf.

Not ideal for

  • Environments without DSH 0.1.0-rc.5-compatible runtime, Node.js 22.19+, or an Overleaf Git integration token.
  • Workflows that need the plugin itself to compile LaTeX, inspect rendered PDFs, or automate the Overleaf browser UI.
  • Users who cannot restart DSH after changing project configuration, which is read only at startup.

README

dsh-overleaf

English 中文

Connect multiple Overleaf projects to DeepSeek Harness (DSH) through OverleafMCP.

dsh-overleaf installs OverleafMCP 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.5 or a compatible release.
  • Node.js 22.19.0 or newer.
  • An Overleaf Git integration token.

Install

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

If the DSH CLI is installed and available on PATH:

dsh plugin --profile web add dsh-overleaf
dsh web

The npm installation command becomes available after this package is published.

Configure

The plugin uses dsh-overleaf.config.json next to its index.js. If the file is missing, the plugin creates it on startup with this content. 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 OverleafMCP project configuration. Do not edit the generated .dsh-overleaf.projects.json 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.

Frequently Asked QuestionsFAQ

Use the verified command dsh plugin --profile default add github:fly233338/dsh-overleaf in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.