Tooldash Mcp

io.github.LassiB999Published by GitHub account LassiB999v1.0.2Updated Oct 24, 2026

Offline PDF and text tools: merge, extract pages, inspect, clean text. No upload, no API key.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

An offline MCP server that lets an assistant inspect, merge and extract pages from PDFs and clean up text, all locally on your machine.

What you can do
Inspect a PDF: page count, per-page dimensions and metadata without writing anything to disk (pdf_info). Merge two or more PDFs into one in a given order, or copy a page selection into a new PDF, with overwrite protection unless explicitly allowed. Clean text: collapse whitespace and blank lines, strip invisible characters, normalize punctuation, optionally remove URLs. Errors such as missing files, password-protected PDFs or out-of-range pages come back as readable messages instead of crashing the server.
When to use it
Useful when you want an assistant to handle PDFs and text without uploading documents to a third-party service, for example combining reports, pulling out page ranges, or tidying copied text. A good fit for confidential documents that should stay on the local machine.
Requirements
Runs as a local stdio process started by your MCP client, typically via npx; Node.js 20 or newer is required. No account, API key or network access. Optionally set TOOLDASH_MCP_ROOT to confine all file reads and writes to one directory.
Before you install
Without TOOLDASH_MCP_ROOT the server reads and writes anywhere your user account can, so set it to limit access. merge_pdfs and extract_pdf_pages write files and will replace an existing file only when overwrite is set to true. clean_text with removeUrls strips every http/https URL and cannot check whether a link works.

Installation

In SourceWeft

  1. Open Tooldash Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ToolDash MCP

Offline PDF and text tools for AI agents. An MCP server that lets Claude Desktop, Cursor, VS Code and any other MCP client merge PDFs, pull out pages, inspect documents and clean up text — entirely on your own machine.

No upload. No API key. No account. No network call of any kind: the PDF work is done locally by pdf-lib, so a confidential contract never leaves your laptop.

[Powered by ToolDash]

Tools

ToolWhat it doesWrites files?
pdf_infoPage count, per-page dimensions and metadata of a PDFNo
merge_pdfsCombine two or more PDFs into one, in the given orderYes
extract_pdf_pagesCopy a page selection ("1-3,7,10-12") into a new PDFYes
clean_textCollapse whitespace, strip invisible characters, normalize punctuation, optionally remove URLsNo

The two tools that write files refuse to replace an existing file unless you pass overwrite: true, so an agent retrying a call cannot quietly destroy a document.

Requirements

Node.js 20 or newer.

Install

No install step — your MCP client runs it on demand with npx. Add the server to your client's config and restart it.

Claude Desktop

Edit claude_desktop_config.json:

  • macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%\Claude\claude_desktop_config.json
  • Linux — ~/.config/Claude/claude_desktop_config.json
json
{  "mcpServers": {    "tooldash": {      "command": "npx",      "args": ["-y", "tooldash-mcp"]    }  }}

Restart Claude Desktop. The tools appear under the tools icon in the chat box.

Cursor

Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project):

json
{  "mcpServers": {    "tooldash": {      "command": "npx",      "args": ["-y", "tooldash-mcp"]    }  }}

Then enable the server under Settings → MCP.

VS Code (GitHub Copilot agent mode)

Create .vscode/mcp.json:

json
{  "servers": {    "tooldash": {      "type": "stdio",      "command": "npx",      "args": ["-y", "tooldash-mcp"]    }  }}

Running from a clone

bash
git clone https://github.com/LassiB999/tooldash-mcp.gitcd tooldash-mcpnpm installnpm test

Then point your client at node /absolute/path/to/tooldash-mcp/server.js instead of npx.

Paths may be absolute, relative to the client's working directory, or start with ~. Surrounding quotes are stripped, so a path pasted as "/home/you/file.pdf" still works.

Restricting file access

The server reads and writes wherever your user account can. To confine it to one directory, set TOOLDASH_MCP_ROOT — any path outside it is refused with a clear error:

json
{  "mcpServers": {    "tooldash": {      "command": "npx",      "args": ["-y", "tooldash-mcp"],      "env": { "TOOLDASH_MCP_ROOT": "/home/you/Documents/pdfs" }    }  }}

Usage examples

Ask your assistant in plain language — "merge these two PDFs and put the result on my desktop" — and it will fill in the calls below. The raw JSON is here for testing.

pdf_info

json
{ "path": "/home/you/Documents/report.pdf" }
report.pdf: 12 page(s), 248.3 KB. Title: "Q3 Report".

merge_pdfs

json
{  "inputPaths": ["/home/you/Documents/cover.pdf", "/home/you/Documents/report.pdf"],  "outputPath": "/home/you/Documents/final.pdf",  "overwrite": false}

extract_pdf_pages

Pages are 1-based. Order is preserved, so "3,1-2" gives you page 3 first. A descending range like "5-1" reverses those pages.

json
{  "inputPath": "/home/you/Documents/report.pdf",  "pages": "1-3,7,10-12",  "outputPath": "/home/you/Documents/excerpt.pdf"}

clean_text

json
{  "text": "Hello   world  \r\n\r\n\r\n\r\nSecond   line   ",  "collapseBlankLines": true,  "normalizeQuotes": false,  "removeUrls": false}

removeUrls strips every http/https URL. The server is offline, so it cannot tell a working link from a dead one — it does not pretend to.

How it handles failure

Bad input comes back as a readable error result the model can act on, never as a crash: a missing file, a password-protected PDF, a page number past the end of the document, or an output path that already exists each produce a message saying what to do next. The server keeps running.

Diagnostics go to stderr only. stdout carries protocol frames and nothing else — the tests would fail if anything leaked into it.

Development

bash
npm test                # 15 end-to-end tests: a real MCP client over stdio, on real PDFsnpm run inspect         # open the MCP Inspector against this server

Powered by ToolDash

ToolDash is a set of free, browser-based utilities — PDF, text, image, colour, developer and calculator tools — that run entirely in your tab with nothing uploaded. This server brings the same idea to your editor.

License

MIT

Source: README.md at commit 7fe06d2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts