Log inSubmit server
Epo Ops logo

Epo Ops

Searches EPO patent records and retrieves bibliographic, family, abstract, claims, and legal-status data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Epo Ops

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "epo-ops": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epo-ops"
      ],
      "env": {
        "PLATFORM_EPO_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Epo Ops MCP server exposes European Patent Office Open Patent Services data through MCP tools for searching published patents and examining individual records. It supports CQL queries, DocDB, epodoc, and original patent-number formats, with access to bibliographic data, abstracts, claims, INPADOC families, and legal-status events. Use it for worldwide patent research involving European publications and related international filings; use a USPTO-focused source for US-only searches. It can run through the Pipeworx gateway or locally as a stdio MCP server.

Use cases

  • Search published patents with CQL queries
  • Inspect claims and abstracts for a patent
  • Trace related applications across jurisdictions
  • Review legal-status events by family member
  • Retrieve bibliographic data for a publication

Key features

  • CQL patent search
  • EPO bibliographic records
  • INPADOC family relationships
  • Abstract and claims retrieval
  • Legal-status event lookup
  • Gateway or local stdio deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

5/5 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @pipeworx/mcp-epo-ops (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads977Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.

How Epo Ops works

What Epo Ops MCP server does

Epo Ops MCP server connects AI agents to the European Patent Office Open Patent Services (OPS) endpoint. Its data covers published patents in the EPO worldwide patent register, using DocDB records and INPADOC family relationships to connect related applications across jurisdictions. The integration is independent and unofficial; it is not published or endorsed by the European Patent Office.

The server is intended for patent discovery and record inspection. It can search published patents with CQL, then retrieve information for a specific publication or application. Available record data includes bibliographic details, abstracts, claims, worldwide family members, and legal-status events such as grants, lapses, oppositions, withdrawals, appeals, and renewal-fee activity.

How it works

The gateway deployment exposes the pack at https://gateway.pipeworx.io/epo-ops/mcp. That endpoint lists the Epo Ops tools together with Pipeworx shared tools, including routing and discovery tools. The full Pipeworx gateway is another option; both gateway URLs use the same underlying catalog, while the pack endpoint lists this pack's tools directly alongside the shared gateway set.

A local package is also available through npx -y @pipeworx/mcp-epo-ops. In that mode, the process communicates over standard input and output and exposes only the Epo Ops tool set. The local and gateway variants use the same EPO source and capabilities, but only the gateway provides Pipeworx-wide routing through tools such as ask_pipeworx.

For clients or scripts that do not use MCP, the gateway provides HTTP tool calls. A search can be sent to the corresponding /v1/tools/epo_ops_search_patents endpoint with a JSON body containing a query.

Setup and configuration

Add the gateway MCP URL to a compatible client, or configure the local command as an stdio server. The local option does not require a Pipeworx account. Gateway authentication uses a platform credential supplied as PLATFORM_EPO_KEY, formatted as consumer_key:consumer_secret, or a consumer key and secret can be passed with the apiKey query parameter after registering with the EPO developer portal.

The integration exchanges the credentials for an OAuth2 bearer token. Tokens remain valid for 20 minutes and are cached. EPO responses use JSON, and the upstream base URL is https://ops.epo.org/3.2/rest-services/.

Patent identifiers can use EPO DocDB notation such as EP.1234567.A1, epodoc notation such as EP1234567, or an original publication format such as EP1234567B1.

Tools and capabilities

The Epo Ops MCP server provides these pack-specific operations:

  • search_patents(query, range?) runs a CQL search over published patent records.
  • get_biblio(number, format?) returns bibliographic information.
  • get_family(number) finds related applications through INPADOC family data.
  • get_abstract(number) retrieves abstract text.
  • get_claims(number) retrieves claims text.
  • get_legal_status(number) returns INPADOC legal-status information grouped by family member and contracting state.

The gateway may show more tools than this list because shared Pipeworx meta-tools are included on pack endpoints. The local stdio package is limited to the six pack-specific operations above.

Limitations and notes

This source is designed around EPO OPS and worldwide related filings, not a dedicated US-only patent service. The README specifically distinguishes it from a USPTO ODP patents pack, including differences in claims and citation coverage. Search results and returned fields depend on the EPO source and the identifier supplied. Gateway routing requires the Pipeworx deployment, while the local package avoids that gateway round trip but does not provide cross-catalog routing.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Epo Ops

Epo Ops is an MCP server that connects AI agents to the European Patent Office Open Patent Services and its worldwide patent register. Its main tools search published patents, retrieve bibliographic data, abstracts, and claims, find INPADOC families, and inspect grouped legal-status events for related filings.

Install it locally with `npx -y @pipeworx/mcp-epo-ops` and configure that command as an MCP stdio server. You can instead add `https://gateway.pipeworx.io/epo-ops/mcp` to an MCP client for the hosted gateway deployment.

Yes, Epo Ops works with Cursor through the hosted MCP URL. Add `https://gateway.pipeworx.io/epo-ops/mcp` to Cursor's MCP configuration; the gateway exposes the pack tools along with shared Pipeworx meta-tools.

The hosted gateway accepts `PLATFORM_EPO_KEY` as a `consumer_key:consumer_secret` value, or an EPO credential can be supplied with the `apiKey` query parameter. The local stdio package does not require a Pipeworx account, while EPO credentials are obtained through the EPO developer registration process.

Epo Ops can cover related filings in many jurisdictions through INPADOC family data, but the README directs US-only searches to a separate USPTO ODP patents pack. Its primary source is the EPO worldwide patent register.

Related MCP servers

All in Legal All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewEpo Ops AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/epo-ops?style=directory)](https://allmcps.com/mcp/epo-ops)
HTML Embed
<a href="https://allmcps.com/mcp/epo-ops"><img src="https://allmcps.com/api/badge/epo-ops?style=directory" alt="Epo Ops on AllMCPs" /></a>