Patent Connector: MCP Server for AI-Powered Patent Research

Wolfgang Stark

26 Oct 2025 — 1 min read

I've built Patent Connector, a Model Context Protocol server now in open beta. It connects ChatGPT Desktop, Claude Desktop, and other MCP-compatible AI tools directly to patent databases - starting with the free EPO OPS API.

The Problem with Web Search

Tools like ChatGPT can access Google Patents through web search, but that approach is far from optimized. AI models frequently confuse dates, misinterpret publication versus filing dates, or extract incomplete claim text from HTML. Direct API integration provides structured, validated data that the AI can process reliably.

Beyond Single-Provider Access

The multi-provider architecture offers practical advantages. You're not locked into Google Patents if you prefer not to send queries through their systems. Privacy-conscious users can route requests through EPO or other providers instead.
More importantly, you can combine data from multiple sources in a single conversation. Cross-reference EPO family data with USPTO prosecution history, or verify publication dates across jurisdictions. Each provider brings different strengths - EPO for European cases, USPTO for detailed file histories, Lens for broad coverage.
The system isn't limited to retrieval either. Future provider integrations will support management operations - save patents to Lens collections or track legal status changes. The MCP protocol handles both read and write operations equally well.

Technical Implementation

Patent Connector eliminates the need to copy patent numbers between your AI chat and web browsers. Natural conversations where the AI retrieves patent data in real-time - claims, prior art searches, family analysis - with API calls handled automatically through the MCP protocol.

I designed the architecture with encrypted credential storage and personal access tokens for MCP clients. A web UI manages provider credentials and token generation. The system currently supports EPO OPS, with LENS.ORG and USPTO integrations coming soon.

Try it: patent.dev/patent-connector
Status: Open Beta (free EPO OPS access)

Working on patent data integration or need guidance on building robust API clients? I specialize in this exact intersection of patent information systems and modern software architecture.

EPO OPS v3.2 Go Client Library

I've released a complete Go client for the European Patent Office's Open Patent Services API v3.2. The library provides access to patent bibliographic data, full-text documents, search capabilities, family information, and legal status data. Building on Official Specifications I started with EPO's official

EPO BDDS Go Client Library Released

I've released a new Go client library for the European Patent Office Bulk Data Distribution Service. The library provides straightforward access to EPO's bulk patent data products through a clean, production-ready Technical Approach Since no official API specification existed for BDDS, I created an OpenAPI v3

USPTO Open Data Portal

Great news for patent data enthusiasts! The USPTO has launched its Open Data Portal (ODP), making it faster and easier to access patent and trademark datasets. Whether you're a researcher, developer, or just a data geek, this platform simplifies the way you retrieve and customize USPTO data. The

Patent claim dependencies and LLMs

It's been a while since my last post - lots of things are happening in parallel. Besides my day-to-day work, I'm currently building an international patent online community - a place where professionals and anyone interested in patents can meet, share ideas, and chat. On top