Tooldash MCP vs Filesystem
A side-by-side look at the Tooldash MCP and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tooldash MCP for file systems work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tooldash MCP when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pdf_info, merge_pdfs, extract_pdf_pages.
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 51/100 · Good | 76/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,405 |
| Directory activity | 1 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Tooldash MCP | View Filesystem |
Tools & capabilities
Tooldash MCP tools 4
pdf_infoPage count, per-page dimensions and metadata of a PDFmerge_pdfsCombine two or more PDFs into one, in the given orderextract_pdf_pagesCopy a page selection (`"1-3,7,10-12"`) into a new PDFclean_textCollapse whitespace, strip invisible characters, normalize punctuation, optionally remove URLs
Filesystem tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Tooldash MCP
{
"mcpServers": {
"tooldash-mcp": {
"command": "npx",
"args": [
"-y",
"tooldash-mcp"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Tooldash MCP is categorized under File Systems and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Tooldash MCP for file systems work and Filesystem for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Tooldash MCP has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tooldash-mcp and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tooldash MCP has a quality signal of 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Filesystem has 76/100 (Great) with 8 views, 0 installs and 91,405 GitHub stars.
