Pdf Card MCP vs Hledit MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Pdf Card MCP vs Hledit MCP
In-depth architectural comparison of the Pdf Card MCP and Hledit MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Pdf Card MCP
File Systems · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Hledit MCP
File Systems · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Pdf Card MCP if you need specialized File Systems tools running via a local process. Choose Hledit MCP if your workspace requires File Systems integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Pdf Card MCP when:
You need dedicated capabilities in the File Systems domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the File Systems domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: HLEDIT_BIN, HLEDIT_CWD, HLEDIT_MCP_DIFF, HLEDIT_MCP_DIFF_MAX_LINES, HLEDIT_MCP_DIFF_CONTEXT, HLEDIT_MCP_DIFF_MAX_CELLS.
Converts local PDFs into source-linked, card-based standalone HTML readers with notes, highlights, and static publishing.
Hash-anchored file edits for MCP clients. Reads files with line anchors, validates anchors against current content, and rejects stale writes before changing files.
Pdf Card MCP is categorized under File Systems and uses a local stdio subprocess. In contrast, Hledit MCP belongs to File Systems using local stdio subprocess. Select Pdf Card MCP when you need capabilities focused on file systems and Hledit MCP when you require tools for file systems.
`fixed`, `pdf`, or `sampling`; defaults to `pdf`. `fixed` preserves the
table_engine
`auto`, `pdfplumber`, or `gmft`; `auto` uses `gmft` when installed.
text_engine
`char_geometry` or `pdfplumber_words`; defaults to `char_geometry` so
postprocess_engine
`none` or `sampling`; defaults to `none`. When set to `sampling`,
model_cache_dir
optional cache directory for local ML table model weights.
+1 more tools listed on main page
Hledit MCP Tools (1)
hledit
Read, edit, or batch-edit files using hash-anchored line references (LN#HASH, currently LN#HHH). Use op:'read' to get anchors, op:'edit' for single changes, op:'batch' for multiple edits in one call. Anchors come from the most recent read and detect stale context before any write.