PDF Text Extractor

io.github.sumitrmardyPublished by GitHub account sumitrmardyv1.0.0Updated Oct 26, 2026

Text from PDF links, OCR for scanned pages. One flat row per URL, never null. Billed on success.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant pull text out of PDF links, including OCR for scanned pages.

What you can do
  • Extract text from PDFs supplied as links, with OCR applied to scanned pages.
  • Return results as one flat row per URL, with no null values in the output.
When to use it
Useful when an assistant needs readable text from PDF URLs, especially scanned documents that need OCR, and you want a hosted service rather than local parsing.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. OAuth sign-in is required; clients without OAuth can send an Apify API token in the Authorization header. An Apify account is needed.
Before you install
Usage is billed on success, so extractions cost money. The Authorization header carries an Apify API token, a credential that should be kept private. PDF URLs you submit are sent to Apify's service.

Installation

In SourceWeft

  1. Open PDF Text Extractor in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sumitrmardy%2Fpdf-text-extractor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pdf-text-extractor": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sumitr_mardy/pdf-text-extractor"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 22, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.