Patent Downloader

Created By
Edison-A-N9 months ago
A Python SDK for downloading patents from Google Patents with Model Context Protocol (MCP) support.
Overview

what is Patent Downloader?

Patent Downloader is a Python SDK designed for downloading patents from Google Patents, featuring support for Model Context Protocol (MCP).

how to use Patent Downloader?

To use Patent Downloader, install it via pip or uv, create an instance of the downloader, and call the download method with the patent number.

key features of Patent Downloader?

  • Download patent PDFs from Google Patents
  • Simple and clean API
  • MCP (Model Context Protocol) server support
  • Command-line interface for easy access
  • Type hints and comprehensive error handling

use cases of Patent Downloader?

  1. Researchers downloading patents for analysis.
  2. Developers integrating patent data into applications.
  3. Legal professionals retrieving patent documents for case studies.

FAQ from Patent Downloader?

  • Can I download multiple patents at once?

Yes! You can download multiple patents by providing their numbers in a single command.

  • Is there a command-line interface available?

Yes! Patent Downloader includes a command-line interface for easy usage.

  • How do I set a custom output directory?

You can set the OUTPUT_DIR environment variable to specify a custom output directory for downloaded files.

Server Config

{
  "mcpServers": {
    "patent_downloader": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/Edison-A-N/patent_downloader@0.1.0",
        "--with",
        "patent_downloader[mcp]",
        "patent-downloader",
        "mcp-server"
      ],
      "env": {
        "OUTPUT_DIR": "/Users/nan.zhang/Downloads/patents"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Edison-A-N
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