Skip to main content
Glama
enesjakozh
truaxki

PDF to PNG MCP Server

by truaxki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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 poppler

  • Linux : sudo apt-get install poppler-utils

Related MCP server: MCP PDF Reader

インストール

  1. このリポジトリをクローンします:

    git clone https://github.com/truaxki/mcp-Pdf2png.git
cd mcp-Pdf2png

  2. 仮想環境を作成してアクティブ化します。

    uv venv
# Windows
.venv\Scripts\activate
# Unix/macOS
source .venv/bin/activate

  3. パッケージをインストールします。

    uv pip install -e .

使用法

1. MCPクライアントを構成する

claude_desktop_config.jsonにサーバー設定を追加します。このファイルは通常、以下の場所にあります。

  • Windows: %APPDATA%\Claude Desktop\config\claude_desktop_config.json

  • macOS/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などになります。

  • コンバージョン数を含む成功メッセージを返します

貢献

貢献を歓迎します！お気軽にプルリクエストを送信してください。

Available Tools

1 tool
pdf2pngC

Converts PDFs to images in PNG format.

ParametersJSON Schema
NameRequiredDescriptionDefault
read_file_pathYes
write_folder_pathYes

TDQS

C2.8/5.0
Behavior2/5

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.

Conciseness5/5

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.

Completeness2/5

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.

Parameters2/5

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.

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 ('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.

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, 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. 1 tool updatev1.0.0
    • Addedpdf2png
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clearly defined.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • PDF Reader MCP Server

    pablontiv
    F
    license
    A
    quality
    Not graded
    maintenance
    A Model Context Protocol server that extracts and processes content from PDF documents, providing text extraction, metadata retrieval, page-level processing, and PDF validation capabilities.
    4
    1
    -

  • MCP PDF Reader

    rturv
    A
    license
    A
    quality
    C
    maintenance
    A 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.
    7
    10 npm
    1
    MIT

  • MD-PDF MCP Server

    kareemaly
    F
    license
    A
    quality
    D
    maintenance
    An 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.
    5
    1
    -

  • pdf-mcp

    angshuman
    A
    license
    Not graded
    quality
    D
    maintenance
    An 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 npm
    ISC

Appeared in Searches