PDF to PNG MCP Server
PDF 转 PNG MCP 服务器
提供 PDF 到 PNG 转换功能的模型上下文协议 (MCP) 服务器。此服务器允许您通过简单的 MCP 工具调用将 PDF 文档转换为 PNG 图像。
先决条件
此服务器需要模型上下文协议 (MCP)。如果您是 MCP 新手,请先安装 SDK:
uv pip install mcp其他要求:
Python 3.10 或更高版本
uv包管理器
poppler(pdf2image 所需)
安装 Poppler
Windows :从poppler-windows下载并安装
macOS :
brew install popplerLinux :
sudo apt-get install poppler-utils
Related MCP server: MCP PDF Reader
安装
克隆此存储库:
git clone https://github.com/truaxki/mcp-Pdf2png.git cd mcp-Pdf2png创建并激活虚拟环境:
uv venv # Windows .venv\Scripts\activate # Unix/macOS source .venv/bin/activate安装软件包:
uv pip install -e .
用法
1. 配置 MCP 客户端
将服务器配置添加到claude_desktop_config.json文件中。该文件通常位于:
Windows:
%APPDATA%\Claude Desktop\config\claude_desktop_config.jsonmacOS/Linux:
~/.config/Claude Desktop/config/claude_desktop_config.json
{
"mcpServers": {
"pdf2png": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/mcp-Pdf2png",
"run",
"pdf2png"
]
}
}
}注意:将/absolute/path/to/mcp-Pdf2png替换为您克隆存储库的实际路径。
2. 使用服务器
服务器提供了一个具有以下参数的单一工具pdf2png :
read_file_path:输入 PDF 文件的绝对路径write_folder_path:PNG 文件保存目录的绝对路径
输出:
每个 PDF 页面都转换为 PNG 图像
文件被命名为
page_1.png,page_2.png,等等。返回包含转换计数的成功消息
贡献
欢迎贡献代码!欢迎提交 Pull 请求。
Available Tools
1 toolpdf2pngC
Converts PDFs to images in PNG format.
| Name | Required | Description | Default |
|---|---|---|---|
| read_file_path | Yes | ||
| write_folder_path | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions conversion but lacks details on permissions, rate limits, error handling, or output behavior (e.g., whether it overwrites files). This leaves significant gaps for a tool that performs file operations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste, front-loading the core functionality. It's appropriately sized for a straightforward tool, earning a high score for conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (file conversion with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address key aspects like what the tool returns, error conditions, or file handling specifics, leaving the agent with insufficient context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate by explaining parameters. It adds no meaning beyond the schema, failing to clarify what 'read_file_path' and 'write_folder_path' represent (e.g., input PDF file path and output directory for PNGs).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 ('converts') and resource ('PDFs to images in PNG format'), making it immediately understandable. It doesn't need to distinguish from siblings since none exist, so a 4 is appropriate rather than a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, prerequisites, or contextual constraints. It merely states what the tool does without indicating appropriate scenarios or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- Added
pdf2png
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clearly defined.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'pdf2png' is descriptive and follows a clear pattern.
One tool is too few for most practical server purposes, as it limits functionality to a single operation. For a PDF conversion server, this feels thin and under-scoped, lacking features like batch processing or format options.
The server is severely incomplete for a PDF conversion domain. It only converts PDFs to PNGs, missing obvious operations like converting to other image formats (e.g., JPEG, TIFF), handling multiple pages, or providing configuration options (e.g., resolution, quality).
Maintenance
Related MCP Connectors
MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.
HTML-to-PDF MCP server — render pixel-faithful PDFs from HTML.
MCP server for detecting and redacting PII (Personally Identifiable Information) in PDF documents.
Hosted MCP server: convert PDFs to clean, LLM-ready Markdown with tables, formulas and OCR.
Related MCP Servers
- FlicenseAqualityNot gradedmaintenanceA Model Context Protocol server that extracts and processes content from PDF documents, providing text extraction, metadata retrieval, page-level processing, and PDF validation capabilities.41-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables the extraction of text, metadata, and embedded images from PDF files. It provides tools for searching text with context, reading specific pages, and counting total pages within a document.710 npm1MIT
- FlicenseAqualityDmaintenanceAn MCP server that enables bidirectional conversion between Markdown and PDF formats, including text extraction from specific pages and metadata retrieval. It supports customizable PDF output sizes and document processing through standard MCP tools.51-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for reading, writing, and manipulating PDF files, including text extraction, metadata retrieval, and merging or splitting documents. It also enables users to create PDFs from plain text and convert specific pages or entire documents into images.37 npmISC