PDF Export for AI Agents

Name: PDF Export for AI Agents
Author: pdfcrowd

Official

by pdfcrowd

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Claude Code Codex Gemini CLI npm version

PDF Export for AI Agents

Well-designed PDFs from a single prompt. Describe what you need, get a professional document.

Example

Analyze this project and create a comprehensive architecture overview PDF.
Include component diagrams and data flow. Save to architecture-overview.pdf

Architecture Overview

More examples →

Related MCP server: Resume Generator MCP Server

Configuration

Prerequisites: Node.js 18 or later.

Claude Code

Option A — Install as a plugin (Recommended):

/plugin marketplace add pdfcrowd/pdfcrowd-mcp-pdf-export
/plugin install pdfcrowd-export-pdf@pdfcrowd

Option B — Register the MCP server:

claude mcp add --scope user pdfcrowd-export-pdf -- npx -y pdfcrowd-mcp-pdf-export

Or add the equivalent JSON to ~/.claude.json (user scope) or .mcp.json (project scope):

{
  "mcpServers": {
    "pdfcrowd-export-pdf": {
      "command": "npx",
      "args": ["-y", "pdfcrowd-mcp-pdf-export"]
    }
  }
}

Codex CLI

codex mcp add pdfcrowd-export-pdf -- npx -y pdfcrowd-mcp-pdf-export

Or add manually to ~/.codex/config.toml:

[mcp_servers.pdfcrowd-export-pdf]
command = "npx"
args = ["-y", "pdfcrowd-mcp-pdf-export"]

Gemini CLI

gemini mcp add -s user pdfcrowd-export-pdf npx -y pdfcrowd-mcp-pdf-export

Or add manually to ~/.gemini/settings.json:

{
  "mcpServers": {
    "pdfcrowd-export-pdf": {
      "command": "npx",
      "args": ["-y", "pdfcrowd-mcp-pdf-export"]
    }
  }
}

Notes

Restart your CLI after configuration to load the server

Personal Credentials

Get started right away — no credentials or signup needed. Output includes a watermark. For watermark-free PDFs, sign up for personal credentials.

Personal credentials can be set in:

Config file ~/.pdfcrowd-mcp:

PDFCROWD_USERNAME=your_username
PDFCROWD_API_KEY=your_api_key

Environment variables PDFCROWD_USERNAME and PDFCROWD_API_KEY.

Privacy

Your source code never leaves your machine — only the rendered document is sent to PDFCrowd for PDF conversion.

License

MIT

Available Tools

2 tools

pdfcrowd_create_pdfCreate PDFA

Idempotent

Export any content (including charts) to PDF. If input isn't HTML, create a well-designed layout first. IMPORTANT: Call pdfcrowd_info(topic: "parameters") to get the full input schema. IMPORTANT: Before creating HTML, first call pdfcrowd_info(topic: "html_layout") to get the layout guidelines. Do NOT pass PDFCrowd API parameters - this tool has its own schema.

On error: Read the error message carefully and follow its guidance. Report configuration issues to the user instead of trying other PDF tools.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide hints (readOnlyHint: false, destructiveHint: false, etc.), but the description adds valuable context beyond these: it explains that non-HTML input requires layout creation first, details error-handling behavior ('Read the error message carefully'), and specifies not to use other PDF tools on configuration issues. This enhances transparency without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose but includes multiple IMPORTANT notes and error-handling instructions that, while useful, make it somewhat verbose. Each sentence adds value (e.g., layout guidelines, error guidance), but it could be more streamlined for better conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (involving HTML layout and external schema references) and lack of output schema, the description is reasonably complete: it covers purpose, prerequisites, error handling, and references to additional info. However, it doesn't detail output format or success behavior, leaving some gaps in contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so the description doesn't need to explain parameters. It mentions calling 'pdfcrowd_info' to get the full input schema, which implies parameters exist but are documented elsewhere. This meets the baseline of 3 for high schema coverage without adding parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Export any content (including charts) to PDF' with a specific verb ('Export') and resource ('PDF'). It distinguishes from the sibling tool 'pdfcrowd_info' by focusing on PDF creation rather than information retrieval. However, it doesn't explicitly differentiate from other potential PDF creation tools beyond mentioning not to use other PDF tools on errors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when and how to use this tool: it instructs to call 'pdfcrowd_info' for parameters and layout guidelines before use, specifies not to pass PDFCrowd API parameters, and gives clear error-handling instructions ('Report configuration issues to the user instead of trying other PDF tools'). This covers when to use alternatives and prerequisites effectively.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

pdfcrowd_infoPDF Export InfoC

Get usage tips and upgrade info for PDF Export

ParametersJSON Schema

Name	Required	Description	Default
`topic`	No	Optional topic for specific guidance. Available: html_layout, mermaid_diagrams, local_assets, parameters

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes a read-only informational operation ('Get usage tips and upgrade info'), which implies it's safe and non-destructive, but it doesn't specify any behavioral traits like authentication needs, rate limits, or what the output format might be (e.g., text, structured data). This leaves significant gaps for an agent to understand how to interact with it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, consisting of a single, clear sentence that directly states the tool's purpose without any wasted words. Every part of the sentence earns its place by conveying essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a simple informational tool with one optional parameter) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., the format or content of the 'usage tips and upgrade info'), which is critical for an agent to use it correctly. The schema covers the input well, but the output remains unspecified, making the overall context insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'topic' parameter fully documented in the schema (including optional nature and available values). The description doesn't add any meaning beyond what the schema provides, as it doesn't mention parameters at all. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('usage tips and upgrade info for PDF Export'), making it immediately understandable. However, it doesn't explicitly differentiate from its sibling tool 'pdfcrowd_create_pdf' (which presumably creates PDFs rather than providing information), so it misses the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool or any other context for usage, leaving the agent to infer based on the tool name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: pdfcrowd_create_pdf is for creating PDFs from content, while pdfcrowd_info is for retrieving usage information and guidelines. There is no overlap in functionality, making it easy for an agent to choose the right tool for each task.

Naming Consistency5/5

Both tools follow a consistent naming pattern with the prefix 'pdfcrowd_' followed by a descriptive verb_noun combination (create_pdf and info). This consistency makes the tool set predictable and easy to understand at a glance.

Tool Count2/5

With only two tools, the server feels thin for its purpose of PDF export for AI agents. While the core PDF creation tool is present, the lack of supporting tools (e.g., for managing PDFs, handling errors beyond info, or advanced formatting) limits functionality and may require agents to work around gaps.

Completeness2/5

The tool set is severely incomplete for PDF export operations. It includes creation and info retrieval but lacks essential tools for updating, deleting, or listing PDFs, as well as tools for handling common PDF tasks like merging or splitting. This will likely cause agent failures in more complex workflows.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

PDFMakerAPI A
io.github.GerardoBarrera
Turn a description into a shareable, editable PDF — invoices, certificates, reports, resumes.
Developer Tools Workplace & Productivity
2
docweave-mcp A
io.github.NicolasMartalog
Generate and read PDFs for AI agents: a generate_pdf and a read_pdf tool, priced per document.
Workplace & Productivity Developer Tools
23
DocuQueue MCP B
io.github.dvcoolarun
Generate PDFs from templates via AI chat. Works with Claude, ChatGPT, Cursor, and any MCP client.
Workplace & Productivity Content Management Systems
1111
Document to JSON – PDF Invoice/Statement/Contract Parser
io.github.fashionmascherine-svg
Turn any PDF into structured JSON via AI + OCR: invoices, bank statements, contracts.
Finance AI & Machine Learning
28

Related MCP Servers

Gen-PDF MCP Server
Developer Tools Content Management Systems Workplace & Productivity
gen-pdf
A
license
Not graded
quality
D
maintenance
Enables AI assistants to generate professional PDF documents from markdown content with advanced typography, syntax highlighting, math equations, dark mode, and customizable styling options.
Updated 6 months ago (2026-03-11 22:55 UTC)
MIT
Resume Generator MCP Server
Workplace & Productivity Developer Tools
AndreaCadonna
A
license
A
quality
C
maintenance
Generates professional PDF resumes using LaTeX templates through natural language descriptions. Supports 9 professional templates, AI-powered resume tailoring, and organized folder management for job applications.
Updated a month ago (2026-08-01 21:22 UTC)
4
23
MIT
rendoc
Workplace & Productivity Developer Tools
yoryocoruxo-ai
A
license
A
quality
C
maintenance
Generate professional PDFs from Claude, Cursor, and other AI tools. Create invoices, contracts, reports, and certificates from templates or inline HTML markup.
Updated 5 months ago (2026-04-14 22:53 UTC)
7
59
1
MIT
pdf-it
Developer Tools
mrslbt
A
license
A
quality
B
maintenance
Turn markdown into designed PDFs with cover page, table of contents, and code blocks that hold across pages. One command from Claude Desktop, Claude Code, Cursor, Cline, Zed, or any MCP-capable client.
Updated 2 months ago (2026-07-10 02:47 UTC)
2
63
1
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pdfcrowd/pdfcrowd-mcp-pdf-export'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

PDF Export for AI Agents

Example

Configuration

Claude Code

Codex CLI

Gemini CLI

Notes

Personal Credentials

Privacy

License

Available Tools

TDQS

TDQS

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Gen-PDF MCP Server

Resume Generator MCP Server

rendoc

pdf-it

Appeared in Searches

Latest Blog Posts

MCP directory API