PatSnap (Patent Analytics) MCP server

Integrates with PatSnap's patent analytics API to provide structured access to patent trends, competitive intelligence, and innovation research through specialized tools for technology scouting and landscape analysis.
Back to servers
Setup instructions
Provider
Kunihiro Setogawa
Release date
Apr 09, 2025
Language
TypeScript
Package
Stats
4.0K downloads
4 stars

The PatSnap MCP server collects patent-related information from PatSnap's API for trend analysis and reporting purposes. It provides various tools to analyze patent trends, identify key players, and understand technology landscapes through the PatSnap Insights API.

Features

This server offers several patent analysis tools:

  • Get Patent Trends: Analyze annual application and issued trends for patents related to specific technology fields or keywords
  • Get Word Cloud: View frequently occurring keywords from recent patents (up to 100 terms)
  • Get Wheel of Innovation: Obtain a hierarchical view of keywords in a technology space
  • Get Most Cited Patents: Identify top 10 most influential patents
  • Get Top Authorities of Origin: Analyze main sources of priority filings
  • Get Top Inventors: Discover the top 10 inventors in a technology field
  • Get Top Assignees: Identify the top 10 companies with largest patent portfolios
  • Get Simple Legal Status: View the breakdown of patent legal statuses
  • Get Most Litigated Patents: Find the top 10 patents involved in litigation cases

Installation

To install the PatSnap MCP server:

# Install the package
npm install @kunihiros/patsnap-mcp

Configuration

The server requires PatSnap API credentials to function. You'll need to set up environment variables for authentication:

export PATSNAP_CLIENT_ID="your_patsnap_client_id_here"
export PATSNAP_CLIENT_SECRET="your_patsnap_client_secret_here"

MCP Host Integration

To integrate this server with your MCP Host, add the following to your cline_mcp_settings.json file:

{
  "mcpServers": {
    "@kunihiros/patsnap-mcp": {
      "command": "npx",
      "args": ["@kunihiros/patsnap-mcp"],
      "env": {
        "PATSNAP_CLIENT_ID": "your_patsnap_client_id_here",
        "PATSNAP_CLIENT_SECRET": "your_patsnap_client_secret_here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Usage

All tools require either keywords or IPC classification to be specified. When both are provided, IPC is typically prioritized.

Examples

Here are examples of how to use some of the available tools:

Patent Trends Analysis

// Get patent application trends for AI-related patents
const trends = await get_patent_trends({
  keywords: "artificial intelligence",
  years: 5
});

Competitive Analysis

// Get top companies in the machine learning space
const topAssignees = await get_top_assignees({
  keywords: "machine learning",
  limit: 10
});

Technology Landscape

// Get word cloud for blockchain technology
const wordCloud = await get_word_cloud({
  keywords: "blockchain",
  limit: 50
});

Service Access

To obtain the required tokens for the PatSnap service, visit PatSnap Open Platform and register for API access.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "kunihiros-patsnap-mcp" '{"command":"npx","args":["@kunihiros/patsnap-mcp"],"env":{"PATSNAP_CLIENT_ID":"your_patsnap_client_id_here","PATSNAP_CLIENT_SECRET":"your_patsnap_client_secret_here"},"disabled":false,"autoApprove":[]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "@kunihiros/patsnap-mcp": {
            "command": "npx",
            "args": [
                "@kunihiros/patsnap-mcp"
            ],
            "env": {
                "PATSNAP_CLIENT_ID": "your_patsnap_client_id_here",
                "PATSNAP_CLIENT_SECRET": "your_patsnap_client_secret_here"
            },
            "disabled": false,
            "autoApprove": []
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "@kunihiros/patsnap-mcp": {
            "command": "npx",
            "args": [
                "@kunihiros/patsnap-mcp"
            ],
            "env": {
                "PATSNAP_CLIENT_ID": "your_patsnap_client_id_here",
                "PATSNAP_CLIENT_SECRET": "your_patsnap_client_secret_here"
            },
            "disabled": false,
            "autoApprove": []
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later