patentorney-mcp
An MCP server for managing patent application drafts. Built with FastMCP and designed for use with AI coding assistants (Windsurf, Claude Desktop, etc.).
Installation
pip install patentorney-mcp
Or with uvx (no install needed):
uvx patentorney-mcp
MCP Client Configuration
For Windsurf / Claude Desktop, add to your MCP config:
{
"mcpServers": {
"patentorney-mcp": {
"command": "uvx",
"args": ["patentorney-mcp"]
}
}
}
On first use, call set_root(path='/absolute/path/to/project') to point the server at the directory containing patent.yaml. All other tools will prompt for this if it hasn't been set.
Tools (8)
| Tool | Purpose |
|---|---|
set_root(path) |
Point at a patent project directory. Must be called first. |
guide(topic?) |
Usage guides. No args → index. |
claim(action, ...) |
Claims: add|get|update|remove|move|rename|tree |
figure(action, ...) |
Figures: add|get|update|remove|move|rename|list |
numeral(action, ...) |
Numerals: add|get|update|remove|lookup|rename|renumber|list |
prior_art(action, ...) |
Prior art & IDS: add|get|update|remove|list|ids_add|ids_list|ids_check |
glossary(action, ...) |
Glossary: add|get|update|remove|list |
export(target, ...) |
Status, validation & export: status|check|claims|drawings_description|claims_latex|drawings_latex|latex |
Any tool called before set_root() returns an error with a hint to call it. All errors include LLM-actionable hints.
Architecture
patent.yaml— single source of truth for structured data (claims, numerals, figures, glossary, prior art)sections/*.tex— prose sections edited directly;claims.texanddrawings-description.texare generated- Stable slug IDs — all entities use kebab-case slugs; presentation numbers computed from list order
- Dual addressing — tools accept slug or current number (e.g.,
claim("get", id="3")orclaim("get", id="mof-synthesis-method")) - File locking —
fcntl.flockfor safe concurrent access from multiple server instances - Structured claims — preamble + transitional + elements (each with numeral associations)
Project Layout
my-patent/
├── patent.yaml # structured data (MCP-managed)
├── sections/
│ ├── field.tex # prose (edit in IDE)
│ ├── background.tex # prose
│ ├── detailed-description.tex # prose
│ ├── abstract.tex # prose
│ ├── claims.tex # GENERATED
│ └── drawings-description.tex # GENERATED
├── figures/
│ └── *.pdf
├── main.tex # document root
└── tome/ # prior art library (optional)
Testing
uv run pytest
License
MIT
Metadata
Release files for patentorney-mcp 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| patentorney_mcp-0.2.2.tar.gz | 102.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| patentorney_mcp-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 144.8 kB
Release files / patentorney_mcp-0.2.2.tar.gz
| Download URL | patentorney_mcp-0.2.2.tar.gz |
|---|---|
| Size | 102.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
067f343caceb93d303e876564d3ab4a614df59a668589edc5f464e07a3f0c731
|
|
BLAKE2b-256 checksum How to use checksums |
b06a5183ac0d0760475b58b7b1f2630e0839b4f84a1f93e5064c09f23bf270e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logRelease files / patentorney_mcp-0.2.2-py3-none-any.whl
| Download URL | patentorney_mcp-0.2.2-py3-none-any.whl |
|---|---|
| Size | 42.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c09f46600621add9fa050dcb1aa552ea93c1b5cf1916f6f285685f94eb03f308
|
|
BLAKE2b-256 checksum How to use checksums |
c222456e51c048bdc7e22f7796e47f8b164a32a63e2bcb73c6fbfbc4a1bef590
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logSecurity for patentorney-mcp 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for patentorney_mcp-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.