Internal Patent Data Connector

Name: Internal Patent Data Connector
Author: patsnap

@patsnap

Internal Patent Data Connector について

PatSnap Internal Patent Data Connector MCP is a Model Context Protocol server that connects AI agents to PatSnap's Internal Patent Data Connector capabilities. Provides a unified connection layer for bringing patent data into internal systems, applications, and automated workflow

基本情報

カテゴリ

データと分析

トランスポート

stdio

公開者

patsnap

投稿者

Patsnap

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "patsnap-internal-patent-data-connector": {
      "url": "https://connect.patsnap.com/cac75e/mcp?apikey=YOUR_API_KEY",
      "type": "streamableHttp"
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Internal Patent Data Connector?

Internal Patent Data Connector is a Model Context Protocol (MCP) server that connects AI agents to PatSnap’s patent data capabilities. It provides a unified connection layer for embedding patent data—including search, legal status, transfer, licensing, pledge, classification, and bibliographic information—into internal systems, applications, and automated workflows. It is designed for system integration, data platforms, and workflow automation.

How to use Internal Patent Data Connector?

Configure the server in your MCP client using the provided JSON block with a streamableHttp transport type and your API key in the URL. Once configured, the server exposes tools that let AI agents query patent data directly.

Key features of Internal Patent Data Connector

Connects AI agents to PatSnap’s patent data connector capabilities.
Supports patent search, legal status, and bibliographic data.
Handles transfer, licensing, pledge, and classification information.
Uses a unified, streamable HTTP transport layer.
Requires only an API key for authentication.

Use cases of Internal Patent Data Connector

Embedding patent search into internal business applications.
Automating patent legal status monitoring in workflow pipelines.
Integrating classification and bibliographic data into data platforms.
Enabling AI agents to retrieve patent licensing and pledge records.
Connecting patent data to existing system integration processes.

FAQ from Internal Patent Data Connector

What data capabilities does the server expose?

It exposes search, legal status, transfer, licensing, pledge, classification, and bibliographic data.

How is the server configured and what transport does it use?

Configuration requires a JSON block with a streamableHttp transport type and an API key in the URL.

Where can I find more information or the source code?

The homepage is at https://open.patsnap.com/marketplace/mcp-servers/patent-connector and the GitHub repository is at https://github.com/patsnap/mcp/tree/main/ip-intelligence/patsnap-internal-patent-data-connector.

What runtime or dependencies are needed?

The README does not specify runtime requirements beyond an MCP client that supports streamableHttp and an API key.

How is authentication handled?

Authentication is handled via an API key that must be included in the server URL.

「データと分析」の他のコンテンツ

HubSpot MCP Server

baryhuang

A Model Context Protocol (MCP) server that enables AI assistants to interact with HubSpot CRM data, providing built-in vector storage and caching mechanisms help overcome HubSpot API limitations while improving response times.

128