# Epo Ops [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/pipeworx-io/mcp-epo-ops  
**GitHub Stars:** 0  
**npm Downloads (last month):** 977  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/epo-ops

## Description
EPO Open Patent Services MCP

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "epo-ops": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-epo-ops"],
    "env": {
      "PLATFORM_EPO_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_EPO_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/epo-ops/readme_