Home  ›  Playgrounds  ›  MCP tool explorer

pdfnative-mcp tool explorer

The tools an AI assistant gets when you wire pdfnative-mcp v1.0.0 into Claude Desktop, Cursor, Continue, Zed, or any other stdio MCP client (Cline, Windsurf, Goose, Gemini CLI…). The server exposes 12 tools — including inspect_pdf, verify_pdf, add_attachment (Factur-X / ZUGFeRD PDF/A-3), and extract_text — a pdfA flag on every document tool, multi-script lang on add_international_text, and a per-tool _meta.apiVersion stability contract. Each card below shows a real example prompt, the tool-call payload your client emits, and a Generate PDF button that produces the very PDF the AI assistant would receive — running the underlying pdfnative library directly in your browser. No API keys, no install, no LLM cost.

For the full integration story (config, security model, signed-document workflow), see the MCP guide.

1. Configure your client

Pick your client. The snippet below is what you paste into its MCP servers config. npx downloads pdfnative-mcp on first use; no global install needed.

Other clients: any tool that speaks the Model Context Protocol over stdio works — Cline, Windsurf, Goose, Aider, LibreChat, Sourcegraph Cody, Gemini CLI, and your own custom client. Use the same command: "npx" / args: ["-y", "pdfnative-mcp"] pair in whatever JSON shape your client expects.

2. Try the tools

Loading pdfnative from esm.sh… this happens once per page load.

The interactive cards below cover the core document-authoring tools. v1.0.0 adds three more that need local files or a real PDF to act on — verify_pdf (CMS + PAdES-T verification), add_attachment (Factur-X / ZUGFeRD into PDF/A-3), and extract_text — so they run best from your own MCP client. See the MCP guide for their schemas.

3. Now ask your AI assistant

Once you've pasted the config snippet above and restarted your client, ask it anything PDF-shaped:

The AI assistant will pick the right tools, fill the JSON arguments, and pdfnative will render the PDF — no code from you.

Resources