Log inSubmit server
Tooldash MCP logo

Tooldash MCP

Offline MCP tools for inspecting, combining, extracting, and cleaning local PDF and text files.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Tooldash MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tooldash-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tooldash-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

  • pdf
  • text-processing
  • offline
  • developer-tools

The tooldash-mcp MCP server gives AI agents local tools for inspecting, merging, and extracting PDF pages, plus cleaning text. It runs through Node.js and communicates with MCP clients over stdio, using local file paths rather than uploads or network services. Reach for it when document processing must stay on the machine, especially for confidential PDFs. An optional root directory restriction can limit file access to a chosen location.

Use cases

  • Inspect PDF dimensions and metadata
  • Merge local PDF files in a chosen order
  • Extract selected pages into a new PDF
  • Clean text before sending it to another tool

Key features

  • Offline local PDF processing
  • PDF metadata and page inspection
  • Ordered PDF merging
  • Page-range extraction
  • Whitespace and punctuation cleanup
  • Optional URL removal

Tools4

What Tooldash MCP lets your agent do. Expand a tool for its parameters.

Self-reported~75 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · tooldash-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads153Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Tooldash MCP works

What tooldash-mcp MCP server does

The tooldash-mcp MCP server exposes four local document utilities to MCP-compatible clients. It can inspect a PDF, combine multiple PDFs, copy selected pages into a new file, and normalize text. PDF operations use local files and do not send documents to an external service. The server does not require an account, API key, or network connection for its processing.

This fits workflows where an agent needs basic PDF manipulation without introducing an upload step. It is also suitable for cleaning text before another local or agent-driven operation, such as removing unwanted links or regularizing punctuation.

How it works

The server is launched on demand with npx and communicates over standard input and output using MCP. A client supplies file paths or text as tool arguments, and the server returns structured results or readable error messages. Paths can be absolute, relative to the client's working directory, or use ~; surrounding quotation marks are removed from pasted paths.

PDF processing is performed locally with pdf-lib. pdf_info reports the document's page count, page dimensions, and metadata. File-writing operations preserve the requested input order and page order. Page selections use one-based numbering and support comma-separated pages and ranges, including descending ranges.

Setup and configuration

Node.js 20 or newer is required. There is no separate installation step when using a client configuration: add a stdio server entry that runs npx -y tooldash-mcp, then restart or enable the server in the client. Configurations are documented for Claude Desktop, Cursor, and VS Code with GitHub Copilot agent mode.

A cloned checkout can be installed with npm install, tested with npm test, and started by pointing the client at node /absolute/path/to/tooldash-mcp/server.js. Set TOOLDASH_MCP_ROOT to restrict reads and writes to one directory. Paths outside that directory are rejected.

Tools and capabilities

  • pdf_info reads PDF page count, per-page dimensions, and metadata without writing a file.
  • merge_pdfs combines two or more PDFs in the supplied order.
  • extract_pdf_pages writes a new PDF from a selection such as 1-3,7,10-12.
  • clean_text collapses whitespace, removes invisible characters, normalizes punctuation, and can remove URLs.

The clean-text options include blank-line collapsing, quote normalization, and URL removal. When enabled, URL removal strips every HTTP or HTTPS URL rather than checking whether a link is active.

Limitations and notes

The tooldash-mcp MCP server is not a PDF editor or an online document service. Password-protected PDFs, missing inputs, invalid page selections, and out-of-range pages return actionable error results while leaving the server running.

Output files are not replaced by default. merge_pdfs and extract_pdf_pages require overwrite: true before replacing an existing path, which prevents an automatic retry from silently destroying a document. Diagnostics are written to stderr, while protocol frames remain on stdout.

The tooldash-mcp MCP server reads and writes wherever the user account has permission unless TOOLDASH_MCP_ROOT is configured. Although processing is offline, local filesystem access should still be limited to an appropriate directory when agents handle sensitive files. The project is released under the MIT license.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tooldash MCP

Its main tools inspect PDF metadata, merge PDFs, extract selected pages into a new PDF, and clean text. It runs locally through Node.js, requires no API key, and does not upload files or make network calls.

Run it through your MCP client's stdio configuration with `npx -y tooldash-mcp`; no separate package installation is needed. Node.js 20 or newer is required. After adding the configuration, restart or enable the server in the client.

Yes, tooldash-mcp works with Cursor through a `.cursor/mcp.json` stdio configuration. Add a server entry that runs `npx` with `-y` and `tooldash-mcp`, then enable the server under Cursor's Settings → MCP.

Yes, PDF processing happens locally and the server makes no network calls. It uses local files for inspection, merging, and page extraction, so documents are not sent to an external API. The server still reads and writes files allowed by the user account unless a root directory is configured.

Set the `TOOLDASH_MCP_ROOT` environment variable to the directory the server may access. Paths outside that directory are refused with an error. This setting can be added to the MCP client's server configuration.

Related MCP servers

All in File Systems All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTooldash MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tooldash-mcp?style=directory)](https://allmcps.com/mcp/tooldash-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tooldash-mcp"><img src="https://allmcps.com/api/badge/tooldash-mcp?style=directory" alt="Tooldash MCP on AllMCPs" /></a>