PDF Manipulation Toolkit

Created By
Sohaib-2a year ago
Comprehensive PDF manipulation toolkit. Merge, split, encrypt, optimize PDFs through natural language commands via MCP protocol.
Overview

What is PDF MCP Server?

PDF MCP Server is a comprehensive toolkit for manipulating PDF files using natural language commands through the MCP protocol, allowing users to merge, split, encrypt, optimize, and analyze PDFs effortlessly.

How to use PDF MCP Server?

To use PDF MCP Server, clone the repository from GitHub, set up the environment, install necessary PDF tools, and integrate it with Claude AI to execute commands like merging or encrypting PDFs using simple conversational phrases.

Key features of PDF MCP Server?

  • Merge, split, and extract pages from PDFs using natural language.
  • Encrypt and decrypt PDFs with AES-256 encryption.
  • Optimize PDFs for web and email.
  • Analyze PDF metadata and structure.
  • Supports various PDF tools like PDFtk and QPDF.

Use cases of PDF MCP Server?

  1. Merging multiple research papers into a single document.
  2. Encrypting sensitive documents for secure sharing.
  3. Splitting large manuals into manageable chapters.
  4. Extracting specific pages for presentations or reports.

FAQ from PDF MCP Server?

  • Can I use PDF MCP Server without programming knowledge?

Yes! You can use natural language commands to perform PDF operations without needing to write code.

  • What PDF tools are required?

You need to install PDFtk and QPDF to utilize all features of the toolkit.

  • Is PDF MCP Server free to use?

Yes! The toolkit is open-source and free to use.

Server Config

{
  "mcpServers": {
    "pdf-tools": {
      "command": "python",
      "args": [
        "path\\to\\pdf-mcp-server\\server.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Sohaib-2
Star
-
Language
-
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