uspto_ptab_mcp

This USPTO PTAB MCP server provides a high-performance interface for PTAB Open Data Portal API access with token-saving context reduction, hybrid document extraction, and cross-MCP integration. It supports secure API key storage, centralized proxy support when used with the USPTO PFWMCP, and a streamlined path for downloading and processing PTAB documents with enhanced context management. You can leverage tool-search optimizations to guide Claude to relevant workflow tools, and obtain focused results through the server's context-reduction capabilities. Use the PTAB-specific proxy settings to route downloads through a unified proxy when the PFWMCP is present, enabling persistent links and cross-MCP workflows. The server is designed to work alongside other USPTO MCPs to unify patent lifecycle analyses across Trials, Appeals, and Interferences, with robust document extraction and OCR fallback when needed.

Prerequisites:

• A machine running Linux or Windows with Python 3.11+ support
• Access to the USPTO API keys and an optional Mistral API key
• uv (Python sandbox runner) or the ability to install it during setup

Step-by-step installation:

1. Clone the repository to your machine (Windows PowerShell as Administrator):

# Windows example (PowerShell)
cd $env:USERPROFILE
git clone https://github.com/john-walkoe/uspto_ptab_mcp.git
cd uspto_ptab_mcp

2. Install uv if not already installed. The setup script can automatically install uv during the Windows setup:

# Run the Windows setup script which installs dependencies including uv
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
.\deploy\windows_setup.ps1

3. Configure your MCP server entry (example configuration for uv):

{
  "mcpServers": {
    "uspto_ptab": {
      "command": "uv",
      "args": [
        "--directory",
        "C:/Users/YOUR_USERNAME/uspto_ptab_mcp",
        "run",
        "ptab-mcp"
      ],
      "env": {
        "USPTO_API_KEY": "your_actual_USPTO_api_key_here",
        "MISTRAL_API_KEY": "your_mistral_api_key_here_OPTIONAL",
        "CENTRALIZED_PROXY_PORT": "none",
        "PTAB_PROXY_PORT": "8083"
      }
    }
  }
}

4. Start the MCP server using the configuration above. If you run into environment variable or path issues, adjust the directory path and keys accordingly. For Windows installations, you may use the provided deploy scripts to automate setup and config merge with Claude Desktop integration.

5. Verify installation by checking the logs and ensuring the PTAB proxy port (8083) is listening, or use the centralized proxy port if you have the PFWMCP installed.

6. For detailed installation and troubleshooting, refer to INSTALL.md in the repository.

Notes and tips:

• CENTRALIZED_PROXY_PORT should be set to a port like 8080 if you have the USPTO PFW MCP installed and using its centralized proxy. Set to none for standalone PTAB usage.
• PTAB_PROXY_PORT defaults to 8083 when running standalone; when PFWMCP is present, PTAB will route through the centralized proxy (port 8080) if configured.
• Securely store API keys: the Windows DPAPI-enabled flow stores keys securely in the OS key store. If you choose a manual plain-text approach, ensure the MCP JSON does not expose keys publicly.
• If you update other USPTO MCPs (PFW, etc.), ensure PTAB integration remains compatible with the updated proxy and tool references as described in MCP_UPDATE_GUIDE.md.
• The MCP supports enhanced document extraction with Mistral OCR fallback for scanned PDFs and secure browser download links to keep API keys safe from exposure.
• When using Claude Desktop integration, you can enable automatic config merging to preserve other MCP servers in your setup.