Skip to content

Choose an installation path

Patent Client Agents supports direct Python use, local MCP clients, native agent plugins, and remote MCP connections. Choose the page that matches where the tools will run.

You want to Use this setup
Add the same local tool package to Claude Code, OpenAI Codex CLI, or Google Antigravity CLI Agent plugin
Import source-specific clients in Python Python library
Run the MCP server from a Python environment Python library with MCP runtime
Configure Claude Desktop, Gemini CLI, Cursor, Windsurf, Cline, Zed, Continue, VS Code, JetBrains, or another MCP client MCP client configurations
Connect ChatGPT, Replit, or another client to an HTTPS endpoint Remote MCP
Try the curated public service without a local install Hosted service

The agent plugin is the shortest local setup for Claude Code, Codex, and Antigravity. It installs the same Satchel-generated package in each host. Use a direct MCP configuration when you need another client or want to control the server command yourself.

After setup, run your first research task to verify a live, source-backed patent lookup without adding an API key or local corpus.

1. Python library

Install the base package when Python code will call the clients directly. The Python library guide covers the package, credentials, the optional trademark-search extra, and a working example.

2. Python library with MCP runtime

Add the [mcp] extra when one Python environment must provide both the client library and the patent-client-agents-mcp command. Continue with the MCP runtime instructions.

3. Agent plugins

Claude Code, OpenAI Codex CLI, and Google Antigravity CLI are equal deployment targets. The agent plugin guide has the install, update, removal, credential, corpus, verification, and troubleshooting steps for all three.

4. Claude Code skill (standalone, library-user)

The standalone ip_research skill is for people writing Python code against the library. It is separate from the agent plugin. See Add the Claude Code library skill.

5. Stdio MCP from any MCP client

Use the MCP client configuration guide for exact stdio and remote settings across supported clients. The local MCP server guide explains the server command, tool surface, downloads, and resource transport.

6. Remote MCP

Cloud clients cannot spawn a local subprocess. Point them at the public hosted service or another HTTPS deployment by following the remote MCP guide.

MPEP / TMEP corpus setup

MPEP, TMEP, and UPC statutes use local SQLite/FTS5 snapshots. The canonical build commands and deployment notes are under Build local corpora.

Getting help