MCP Tools DirectoryAbout this integration
PDF MCP server: generate PDF/A, sign & verify PAdES (LTV), forms, merge, split, encrypt. 28 tools
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.6.0
- Package
- pdfnative-mcp
- Last compatibility test
- Not independently tested
Connect your agent
pdfnative-mcpPublisher README and npm manifest reviewed from pinned captures. Package was not executed and PDF/PAdES conformance claims were not independently tested. Optional credential and egress configuration remains feature-specific.
Capabilities: Generate and inspect PDF and PDF/A documents, Create, read, fill, encrypt, and decrypt PDF forms and files, Sign, timestamp, validate, and verify PAdES documents, Merge, split, extract, annotate, and update PDFs, Preview layouts and extract text or attachments
Connected profiles
Additional details
io.github.Nizoka/pdfnative-mcp
Source ↗ · Checked 2026-09-171.6.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17pdfnative-mcp
Source ↗ · Checked 2026-09-191.6.0
Source ↗ · Checked 2026-09-19Publisher documents a stdio MCP server launched by npx; optional loopback HTTP, sandbox output, caching, and operator-configured signing-validation endpoints are enabled only through environment variables.
Source ↗ · Checked 2026-09-19The default stdio connection requires no service authentication. Optional loopback HTTP has no authentication unless an operator configures PDFNATIVE_MCP_HTTP_TOKEN, and some signing-validation features need operator endpoints or key material.
Source ↗ · Checked 2026-09-19The documented stdio connection launches npx -y pdfnative-mcp; PDFNATIVE_MCP_OUTPUT_DIR is optional and only enables sandboxed file output.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19