MCP Enabled PDF Reader

Created By
Safe-Swiss-Cloud-AGa year ago
Model Context Protocol (MCP) server to read a single pdf document
Overview

What is MCP Enabled PDF Reader?

MCP Enabled PDF Reader is a tool that utilizes the Model Context Protocol (MCP) server to read a single PDF document, allowing users to extract and interact with the content of PDF files.

How to use MCP Enabled PDF Reader?

To use the MCP Enabled PDF Reader, you need to install Claude Desktop or another MCP-enabled AI tool, set up Python, and configure the tool according to the provided instructions. Once set up, you can read PDF documents through the MCP server.

Key features of MCP Enabled PDF Reader?

  • Ability to read any PDF document without a maximum size limit (token limit applies)
  • Integration with MCP-enabled AI tools like Claude Desktop
  • Simple installation and configuration process

Use cases of MCP Enabled PDF Reader?

  1. Reading and extracting information from academic papers in PDF format.
  2. Analyzing legal documents and contracts stored as PDFs.
  3. Assisting researchers in accessing and processing large volumes of PDF data.

FAQ from MCP Enabled PDF Reader?

  • What is the maximum size of the PDF that can be read?

There is no maximum size for the PDF file, but the number of tokens passed to the model will limit the reading capacity.

  • Is there a specific operating system required?

The tool can be installed on both Windows and macOS systems.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can submit issues and pull requests through the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Safe-Swiss-Cloud-AG
Star
0
Language
Python
License
Apache-2.0 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)

6 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago