PDF To Text

io.github.Jim-PansePublished by GitHub account Jim-Pansev0.7.0Updated Oct 24, 2026

Extracts PDF text locally, with macOS PDFKit and Vision OCR fallbacks and optional AI retry.

VerifiedSTDIODesktop onlyFiles & StorageAI & ML

Overview

AI-generated overview

Local MCP server that extracts text from PDFs, using macOS PDFKit and Vision OCR with an optional AI retry.

What you can do
This server gives an assistant the ability to turn PDF files into text. It reads PDFs from a required root directory and extracts their text locally, falling back to macOS PDFKit and Vision OCR when needed. If local extraction is inadequate, an optional AI retry can be enabled with an OpenAI key. Successful extractions can optionally be saved as text files beside the source PDF.
When to use it
Use it when an assistant needs to read or search the contents of PDF documents on a Mac without uploading them to a cloud service. It is a good fit for local document workflows where OCR of scanned pages matters. Skip it if you need cross-platform support or do not have macOS.
Requirements
Runs as a local stdio process, desktop only. Requires an existing directory set in PDF_TO_TEXT_MCP_ROOT, which defines the filesystem namespace for PDF input and text output. Optional settings include OPENAI_API_KEY for AI retry, OPENAI_MODEL (defaults to gpt-5.4-mini), AI_MAX_OUTPUT_TOKENS, WRITE_TEXT, and extraction queue and parallelism limits.
Before you install
The optional OPENAI_API_KEY secret enables an AI retry that sends PDF-derived content to OpenAI; omit it for local-only extraction. WRITE_TEXT causes text files to be written beside source PDFs. The server reads and writes within the directory set by PDF_TO_TEXT_MCP_ROOT, so choose that root carefully.

Installation

In SourceWeft

  1. Open PDF To Text in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

5
  1. v0.7.0LatestOct 15, 2026
  2. v0.6.0Oct 15, 2026
  3. v0.4.5Oct 12, 2026
  4. v0.4.4Oct 11, 2026
  5. v0.4.3Oct 10, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.