Claude Patent Creator plugin
Claude Patent Creator prepares a patent application in Claude Code: prior art search, MPEP checks, drawings and a draft
- 211 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Downloads the rules, builds a local index and calls external patent and paper databases with the user's keys
- The `patent-creator` agent runs up to 80 minutes and writes application and diagram files into the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/claude-patent-creatorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Downloads the rules, builds a local index and calls external patent and paper databases with the user's keys
- The `patent-creator` agent runs up to 80 minutes and writes application and diagram files into the project
This is third-party code. Review the repository files before installing.
What it does
Claude Patent Creator is a Python package with an MCP server and a Claude Code plugin that takes an inventor from an idea to a draft application. Rule search covers the MPEP, 35 USC and 37 CFR, European EPC norms and the PCT. The `search_mpep` tool combines FAISS vector search, BM25 lexical search and a cross-encoder reranker and returns section and page references. Prior art search spans more than 100 million patents worldwide through Google Patents with a SerpApi key, a BigQuery fallback and the USPTO API, plus papers and preprints through OpenAlex, arXiv and Semantic Scholar. Skills check claims against 35 USC 112(b), the specification against 112(a), formalities against MPEP 608 and European requirements under Articles 84 and 83 EPC. The `/create-patent`, `/search-prior-art`, `/full-review` and other commands start guided workflows, the `patent-creator` agent writes a full application in 55–80 minutes and `patent-diagram-generator` draws diagrams through Graphviz. The tool files nothing: a person reviews and decides.
Who it is for. Inventors and small teams who prepare a patent application themselves and want novelty and form checked before turning to a patent attorney.
Good fit when
- Before filing an idea, you ask whether similar patents already exist worldwide
- Claims are checked for definiteness and antecedent basis under 35 USC 112(b)
- A draft application is built from an invention description or a project source code
- Patent diagrams and block charts are needed with no graphic editor
Not a fit when
- You need a legal opinion or an actual filing: the tool prepares a draft and files nothing
- You have under 4 GB free: the package takes about 2 GB and the rules and index about 1 GB more
- Python outside 3.10 to 3.13 with no way to install it
Example request
Find prior art for my energy storage idea and check my claims against 112(b)Limitations
- The author states the tool is not a lawyer and gives no legal advice. Whether an invention is non-obvious and patentable stays with a person.
- `patent-creator setup` takes 5 to 45 minutes, 45 on a laptop without an NVIDIA GPU, Apple Silicon Macs included. A virtual environment is required.
- Google Patents search uses a SerpApi key, and the README names 250 free searches a month. The BigQuery fallback is paid beyond the first free terabyte a month.
- European and PCT paths are checked against norms in built-in indexes, rules change, so check currency against the primary source.
How to disable. Remove the plugin with `/plugin uninstall`, then the `patent-creator-venv` folder and the data directory `~/.local/share/claude-patent-creator`. The MCP entry in the Claude Code config is removed by hand.
FAQ
How do I install Claude Patent Creator?
Create a virtual environment, run `pip install git+https://github.com/RobThePCGuy/Claude-Patent-Creator.git` and `patent-creator setup`, then install the plugin through `/plugin`. Python 3.10 to 3.13 and about 4 GB of space are needed.
Does the tool file the application?
No. It prepares a draft and materials, and a person files and makes the legal calls. The author states it is not legal advice.
Which patent databases does search use?
Google Patents through a SerpApi key, a BigQuery fallback, the USPTO API and EPO OPS for European applications. Papers and preprints come from OpenAlex, arXiv and Semantic Scholar.
What does `/full-review` check?
Claims, specification and formalities in parallel. `/review-claims` for 35 USC 112(b) and `/review-formalities` for MPEP 608 exist separately.
Is a GPU required?
No, but setup on a laptop without NVIDIA takes up to 45 minutes instead of five. The index is built once and a rerun skips completed steps.
Discussion
No questions or reviews yet.
Related
PluginsA plugin and skill with 14 agents for patent work: prior-art search, idea storming, drafting, review and figures in Claude Code and Codex
The skill leads an inventor by dialogue to a CNIPA technical disclosure and exports it to Word with patent figures
Paper2Patent drafts a Chinese patent application from a research paper: claims, specification, drawings and self-checks.
legal-skills: patent skills
legal-skills
Three skills for a US patent application: a 316-item audit, a mock USPTO examination and a design-around check of the claims
Anthropic's legal plugin suite: contracts, privacy, employment, IP, litigation, AI governance and legal education
A Claude Code plugin that writes papers, grants and posters from real literature: source search first, then cited text.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Patent Creator (this card) | no | 211 | |
| Patent CLI | no | 567 | a CLI for patent work, while this is a plugin with MPEP rules and a draft application |
| Paper2Patent | no | 733 | turns a paper into a patent, while this searches prior art and reviews an application |
README in short
The README opens with the honest limits of the tool: it will say no, files nothing and does not replace a lawyer. It then gives a three-step quick start, use cases, how hybrid search works, what setup does, CLI commands, an MCP tools reference, skills, agents, slash commands, configuration and known issues.
README badge
Original SKILL.md
--- name: patent-reviewer description: Expert system for reviewing utility patent applications against USPTO MPEP guidelines. --- # Patent Creator Skill Antecedent checking is disabled by default. Report it as skipped unless `checks_run` includes `antecedent_basis`; retain the reason in `checks_skipped`. Enabling `PATENT_ENABLE_ANTECEDENT_CHECK=1` requires a server restart. Even when enabled, this is a low-confidence pattern check requiring manual review. Comprehensive patent creation system with USPTO MPEP, prior art databases, and USPTO API for complete patent application analysis. ## Patent search providers Use `check_google_patents_status` first, then `search_patents_google` when SerpApi is configured. BigQuery is optional: call any `*_bigquery` tool only after `check_bigquery_status` confirms it is available. Without BigQuery, read the returned patent links for details, CPC codes and family members; use Google Patents keyword/CPC queries for follow-up searches. Mark unavailable details, family coverage and classification searches as unverified. If neither provider is configured, say patent search needs one free key (README Quick Start, Step 3) and run a no-key first screen in the meantime: several `WebSearch` queries restricted to Google Patents (`allowed_domains: ["patents.google.com"]`), then read the closest patent pages with `WebFetch` for claims, dates, CPC codes and citations. Label everything found this way a web first screen, not a prior-art search: web search ranks pages rather than matching claim text and misses much of the record, so a thin or empty result is never evidence of no prior art. A first screen never supports a novelty, obviousness or patentability verdict: in every later assessment, report section or phase that would give one (including any NOVEL / LIKELY NO verdict), write "Not assessed: only a web first screen was run; set up patent search and rerun" instead. ## When to Use Review patent applications for USPTO compliance, analyze claims/specifications/formalities, integrate prior art, get USPTO guidance, assist with patent drafting. ## Quick Review Commands ```bash /full-review # Complete parallel review /review-claims # 35 USC 112b compliance /review-specification # 35 USC 112a compliance /review-formalities # MPEP 608 compliance /create-patent # New patent application ``` ## Available MCP Tools ### MPEP & Regulations - `search_mpep` - Search MPEP, 35 USC, 37 CFR - `get_mpep_section` - Retrieve indexed section content by number. Check `truncated` and `coverage`; the default caps output at 50 chunks and subsection boundaries are approximate. Increase `max_chunks` if needed, and do not claim complete text. ### Patent Search - `search_patents_google` - Full-text search worldwide, claims included (recommended) - `search_patents_bigquery` - Fallback keyword search (~$2 a search) - `get_patent_bigquery` - Get patent details (claims by default; abstract/description opt-in) - `get_patents_bigquery` - Details for up to 50 patents in one query, same cost as one - `search_patents_by_cpc_bigquery` - Search by CPC classification