How do I find my EPO Credentials?

Register for an account at the [**EPO OPS developer portal**](https://developers.epo.org/), create an application, and you will receive your Consumer Key and Consumer Secret. Copy and paste them below.

Does it support legal status checks?

Yes. The `get_patent_legal_status` tool retrieves the current administrative and legal status metadata for specified patent publications.

What format is required for Doc IDs?

The API uses standard EPODOC format (e.g., EP1234567) for patent identifiers across all retrieval tools.

EPO Open Patent Services MCP Server for CrewAI 4 tools — connect in under 2 minutes

Name: EPO Open Patent Services
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 4 Tools Framework

Connect your CrewAI agents to EPO Open Patent Services through the Vinkius — pass the Edge URL in the `mcps` parameter and every EPO Open Patent Services tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="EPO Open Patent Services Specialist",
    goal="Help users interact with EPO Open Patent Services effectively",
    backstory=(
        "You are an expert at leveraging EPO Open Patent Services tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in EPO Open Patent Services "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 4 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About EPO Open Patent Services MCP Server

Empower your AI agent to orchestrate your entire intellectual property research and patent auditing workflow with EPO Open Patent Services (OPS), the authoritative source for European and global patent data. By connecting the EPO OPS API to your agent, you transform complex patent searches into a natural conversation. Your agent can instantly retrieve bibliographic metadata, audit legal statuses, and identify applicants without you ever touching a patent portal. Whether you are conducting competitive intelligence or managing corporate IP constraints, your agent acts as a real-time patent consultant, ensuring your data is always verified and precise.

When paired with CrewAI, EPO Open Patent Services becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call EPO Open Patent Services tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Patent Auditing — Search for thousands of published patents and retrieve high-resolution metadata, including titles, applicants, and publication dates.
Legal Oversight — Audit the current legal status of any patent publication to understand the administrative reach of IP rights instantly.
Bibliographic Discovery — Query detailed bibliographic data for specific Doc IDs to assist in deep-dive archival classification.
Data Intelligence — Retrieve unique patent identifiers and applicant information to maintain strict organizational control over IP data.
Operational Monitoring — Check API status to ensure your patent research workflow is always operational.

The EPO Open Patent Services MCP Server exposes 4 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect EPO Open Patent Services to CrewAI via MCP

Follow these steps to integrate the EPO Open Patent Services MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 4 tools from EPO Open Patent Services

Why Use CrewAI with the EPO Open Patent Services MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with EPO Open Patent Services through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

EPO Open Patent Services + CrewAI Use Cases

Practical scenarios where CrewAI combined with the EPO Open Patent Services MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries EPO Open Patent Services for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries EPO Open Patent Services, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain EPO Open Patent Services tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries EPO Open Patent Services against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

EPO Open Patent Services MCP Tools for CrewAI (4)

These 4 tools become available when you connect EPO Open Patent Services to CrewAI via MCP:

check_api_status

Check if the EPO Open Patent Services are operational

get_patent_bibliographic

Get full bibliographic metadata for a specific patent by Doc ID

get_patent_legal_status

Check the current legal status of a patent publication

search_epo_patents

Search for published patents in the EPO database

Example Prompts for EPO Open Patent Services in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with EPO Open Patent Services immediately.

"Search for patents related to 'electric vehicles' using EPO OPS."

"What is the legal status of patent 'EP1234567'?"

"Get bibliographic details for Doc ID 'US20230000001'."

Troubleshooting EPO Open Patent Services MCP Server with CrewAI

Common issues when connecting EPO Open Patent Services to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

EPO Open Patent Services + CrewAI FAQ

Common questions about integrating EPO Open Patent Services MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.