📚 PDF Reader MCP

Created By
hfrewreefta year ago
An MCP server built with Node.js/TypeScript that allows AI agents to securely read PDF files (local or URL) and extract text, metadata, or page counts. Uses pdf-parse.
Overview

What is PDF Reader MCP?

PDF Reader MCP is an MCP server built with Node.js and TypeScript that allows AI agents to securely read PDF files from local storage or URLs, extracting text, metadata, and page counts effortlessly.

How to use PDF Reader MCP?

To use PDF Reader MCP, clone the repository, install the dependencies, and start the server. You can then send requests to read PDF files either from local paths or URLs.

Key features of PDF Reader MCP?

  • AI Agent Integration for processing PDF files.
  • Text Extraction from PDF documents.
  • Metadata Retrieval including author, title, and creation date.
  • Page Count retrieval for total pages in a PDF.
  • Secure handling of PDF files.

Use cases of PDF Reader MCP?

  1. Document analysis for extracting information from PDFs.
  2. Content generation using extracted text and metadata.
  3. Integration with AI applications for enhanced document processing.

FAQ from PDF Reader MCP?

  • Can PDF Reader MCP handle all types of PDF files?

Yes! It can read and process various PDF files from local storage or URLs.

  • Is PDF Reader MCP secure for sensitive documents?

Yes! The server ensures secure handling of all PDF files, but it's recommended to avoid uploading sensitive documents without proper security measures.

  • How do I integrate PDF Reader MCP with AI agents?

You can use the extracted text and metadata to enhance your AI's capabilities, making it suitable for various applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hfrewreeft
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago