mcp-pdf-parse

Created By
Khush08a year ago
MCP server for parsing data from a pdf url
Overview

what is mcp-pdf-parse?

MCP-PDF-Parse is a Model Context Protocol (MCP) server designed to extract text data from PDF files accessible via URLs.

how to use mcp-pdf-parse?

To use mcp-pdf-parse, you can install it via npm or run it directly using npx. After installation, configure it in your MCP settings to integrate with the Claude Desktop App.

key features of mcp-pdf-parse?

  • Extracts text from PDF files available at specified URLs.

use cases of mcp-pdf-parse?

  1. Extracting text from academic papers in PDF format.
  2. Parsing data from invoices and receipts stored as PDFs.
  3. Automating data extraction from reports and documents for analysis.

FAQ from mcp-pdf-parse?

  • Can mcp-pdf-parse handle all PDF files?

Yes! It can extract text from any PDF file accessible via a URL.

  • Is mcp-pdf-parse free to use?

Yes! It is open-source and free to use.

  • How do I install mcp-pdf-parse?

You can install it using npm or run it directly with npx without installation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Khush08
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago