Updated on April 1, 2026 | Written by Patsnap Team

This guide shows you how to connect Patsnap Open Platform to Claude Desktop using MCP — and what you can do once you’re connected. If you’ve been running patent research manually, copying data between tools, or asking Claude questions it can’t answer because it lacks current patent data, this integration changes that. By the end, you’ll have a working Claude Desktop environment that can query 200M+ patents, map patent families, and run structured IP analysis through natural language — without switching tools or writing custom API code.

To connect Patsnap patent data to Claude Desktop via MCP: register for a free Patsnap Open Platform account at open.patsnap.com to get an API key, then add Patsnap’s MCP server configuration to your Claude Desktop settings file. Once configured, Claude can call Patsnap’s patent search, family analysis, novelty search, and FTO tools directly as part of any conversation — no manual API calls or copy-pasting required.

What Is MCP and Why Does It Matter for Patent Data?

Model Context Protocol (MCP) is an open standard that lets large language models like Claude call external tools and live data sources directly within an agent session. Without MCP, Claude’s patent knowledge is limited to its training data — which has a cutoff date, contains no proprietary IP data, and cannot run structured searches on demand. With an MCP server connected, Claude can query a live patent database mid-conversation, retrieve structured results, and reason over them in the same response.

For IP professionals and R&D engineers, this is significant. Tasks that previously required switching between a patent database, a spreadsheet, and an LLM — such as running a prior art search, mapping a competitor’s patent family, or drafting a technology landscape summary — can now be handled within a single Claude Desktop session. Patsnap’s MCP servers are built specifically for this workflow, exposing structured patent intelligence rather than raw data.

How to Connect Patsnap MCP to Claude Desktop

The setup process takes under 15 minutes for a standard installation:

1. Create a Patsnap Open Platform account — Register at open.patsnap.com. The free Starter tier includes 10,000 credits with no credit card required, which is sufficient to evaluate the integration and run initial workflows.
2. Generate your API key — From the developer portal, create an API key. This key authenticates all MCP requests from Claude Desktop to Patsnap’s servers.
3. Configure Claude Desktop — Open your Claude Desktop MCP configuration file and add Patsnap’s MCP server endpoint alongside your API key. Patsnap’s developer guides provide the exact configuration block; the process follows the same pattern as other MCP server installations.
4. Select your MCP servers — Patsnap offers 20+ specialized MCP servers covering different data domains. For most R&D and IP workflows, starting with the Patent & Literature Search and Novelty Search servers covers the majority of use cases. Additional servers for life sciences, chemical data, and patent analytics can be added as needed.
5. Test in the Playground — Before building workflows, use Patsnap’s Playground environment to verify your API key is returning live data. This confirms the connection is working before you rely on it inside Claude.

Once configured, Patsnap MCP servers appear as available tools in Claude Desktop. Claude selects the appropriate tool automatically based on the task described in your message.

What You Can Do: Patent Family Mapping as a Live Example

Patent family mapping — identifying all related filings that share a common priority date across multiple jurisdictions — is one of the most direct demonstrations of what this integration enables. Traditionally, mapping a patent family requires querying a database, exporting results, and manually tracing priority linkages across jurisdictions. With Patsnap connected to Claude Desktop, the same workflow runs through a single natural language prompt.

A typical session might look like this: you paste a patent number into Claude Desktop and ask it to map the full family, identify which jurisdictions the assignee has filed in, and flag any lapsed or abandoned members. Claude routes the query to Patsnap’s patent data MCP server, retrieves family data covering 170+ patent authorities, and returns a structured summary — including jurisdiction coverage, legal status per member, and a note on any gaps in key markets. What previously took 30–60 minutes of manual cross-referencing now completes within the conversation.

The same approach applies to competitive intelligence. Asking Claude to “identify the three largest patent families held by [competitor] in battery technology filed after 2020” produces a structured breakdown drawn from live Patsnap data — not a hallucinated summary based on training data. The World Intellectual Property Organization and the European Patent Office publish family data through their own portals, but neither exposes it through an MCP interface that Claude can call natively.

Other Use Cases Unlocked by the Integration

Patent family mapping is one workflow among many. Once Patsnap’s MCP servers are connected, the same natural-language interface applies to:

• Novelty search — Describe a technical concept and ask Claude to retrieve prior art, extract distinguishing features, and assess novelty against the identified references.
• Freedom-to-operate (FTO) analysis — Ask Claude to identify patents in a target jurisdiction that may cover a specific product feature, with structured output organized by risk level.
• Technology landscape mapping — Request a breakdown of filing trends, key assignees, and technology clusters in a defined domain over a specified time range.
• Life sciences and chemical data — For pharma and materials R&D teams, additional MCP servers expose clinical trial data, compound structures, biosequence search, and drug pipeline intelligence through the same interface.

Each of these workflows runs through Claude’s natural language interface, with Patsnap’s domain-specific models handling the patent interpretation layer that general-purpose LLMs cannot provide reliably.

Foire aux questions

Do I need coding experience to connect Patsnap MCP to Claude Desktop?

No. The configuration requires editing a JSON settings file to add the MCP server endpoint and your API key — a process that takes a few minutes and follows a documented template. Patsnap’s developer guides walk through each step. No programming knowledge is required beyond copying and editing a configuration block.

How is querying patent data through Claude different from using a patent database directly?

A patent database returns raw search results — lists of documents, metadata, and text. Claude with Patsnap MCP connected interprets those results: it can extract the relevant claim language, compare results across multiple queries, synthesize a novelty assessment, or generate a structured report — all within the same conversation. The database handles data retrieval; Claude handles reasoning over the data.

Which Patsnap MCP servers should I install first?

For most IP and R&D workflows, the Patent & Literature Search and Novelty Search Lite servers cover the broadest range of tasks. If your work involves life sciences, add the Pharma Intelligence or Biology Modality servers. For competitive analytics and patent landscape work, the Patent Visual Analytics and Patent Landscape Analytics servers are the relevant additions. The full catalog of 20+ servers is available at open.patsnap.com/marketplace/mcp-servers.

Is there a free way to test the integration before committing to a paid plan?

Yes. The Starter tier provides 10,000 free credits with instant API key access — no credit card required. This is enough to run a full patent family mapping session, several novelty searches, and test the Claude Desktop configuration end to end. The Playground environment also lets you test live API responses directly before configuring Claude Desktop.

What if I want to use Patsnap’s patent intelligence without setting up an MCP integration?

If you prefer a ready-to-use interface over a developer setup, Patsnap Eureka provides the same patent intelligence through a web and desktop application — no API key or configuration required. Eureka covers novelty search, FTO analysis, patent drafting, and technology landscape analysis through a purpose-built UI. The MCP integration and Eureka access different entry points to the same underlying data and AI capabilities.