mcp-pdf-tools

Provides an MCP server that offers PDF manipulation tools such as merging PDFs, extracting pages, and searching for/locating related PDFs via text/regex-based approaches.

Evaluated Mar 30, 2026 (22d ago)
Repo ↗ Infrastructure mcp pdf python automation document-processing
⚙ Agent Friendliness
41
/ 100
Can an agent use this?
🔒 Security
22
/ 100
Is it safe for agents?
⚡ Reliability
21
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
30
Error Messages
0
Auth Simplicity
90
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
20
Scope Granularity
10
Dep. Hygiene
45
Secret Handling
30

No auth/authorization model is described for the MCP server. Since MCP is invoked locally (per README), security posture likely depends on local host controls rather than app-level enforcement. TLS is not applicable/undocumented for a local MCP process. The tooling processes potentially untrusted PDFs; without sandboxing/validation details, risk of malicious PDF payloads (e.g., parser vulnerabilities) cannot be ruled out.

⚡ Reliability

Uptime/SLA
0
Version Stability
35
Breaking Changes
30
Error Recovery
20
AF Security Reliability

Best When

Used as a local/controlled MCP tool for document ingestion and basic transformations orchestrated by an agent.

Avoid When

Avoid in untrusted multi-tenant environments or where sensitive PDFs require explicit access controls and audit guarantees (not described).

Use Cases

  • Merge multiple PDF documents into one in a specific order
  • Extract selected pages from a PDF for downstream processing
  • Search within PDFs and/or locate related documents based on extracted text and regex matching
  • Automate PDF workflows from an LLM using the Model Context Protocol (MCP)

Not For

  • Replacing a full-featured PDF editing suite (layout editing, form filling, annotations, etc.)
  • High-assurance or compliance-critical document processing without additional validation/testing
  • Use where strict authentication/authorization controls for the tool are required (not documented)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication mechanism is described. MCP usage appears to be via a local command invocation (e.g., for Claude Desktop), implying access control may rely on local environment/network controls.

Pricing

Free tier: No
Requires CC: No

Pricing not mentioned; project appears to be open-source tooling.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • README does not describe the MCP tool names, input/output schema, or how files are passed/returned—agent integrations may require inspecting the source.
  • No guidance on filesystem access boundaries, output naming, or handling of existing files.
  • Project is marked 'WORK IN PROGRESS - USE WITH CAUTION', suggesting possible instability or incomplete behavior.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-pdf-tools.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered