mcpField
I
Internal Patent Data Connector

Internal Patent Data Connector

Remote
github.com/patsnapData & Analytics70Updated 10w ago
Repository

About Internal Patent Data Connector

Internal Patent Data Connector is a Patsnap MCP server that links AI agents to patent data capabilities. It targets system integration, data platforms and workflow automation, helping teams embed patent data into existing business processes.

Key features

  1. 01Semantic, keyword, identifier and fielded search
  2. 02Full record and supporting detail retrieval
  3. 03Legal status, transfer, licensing and pledge data
  4. 04Classification and bibliographic data access
  5. 05Summarizing, comparing and counting retrieved results

Use cases

  1. 01Bringing patent data into internal systems and data platforms
  2. 02Calling patent search and detail lookups in automated workflows
  3. 03Summarizing search results and suggesting follow-up queries

MCP support

This is a remote MCP server reached over streamableHttp, exposing patent search, detail and legal status capabilities to MCP clients. Access requires an API key included in the connection URL.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://connect.patsnap.com/cac75e/mcp?apikey=YOUR_API_KEY
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Internal Patent Data Connector

by Patsnap

Product Definition

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 workflows. It exposes commonly used capabilities such as search, legal status, transfer, licensing, pledge, classification, and bibliographic data so patent data can be embedded into existing business processes more easily. It is suitable for system integration, data platforms, and workflow automation.

Quick Links

Data Sources and Coverage

Powered by Patsnap data services and enterprise-connected patent data workflows. Coverage depends on enabled internal data connectors, account permissions, and API key scope.

Supported Tools

  • Search and discovery: semantic, keyword, identifier, or fielded search workflows
  • Retrieval and detail: fetch complete records or supporting details when available
  • Analytics and synthesis: summarize, compare, count, or structure retrieved results

Installation

{
  "mcpServers": {
    "internal_patent_data_connector": {
      "url": "https://connect.patsnap.com/cac75e/mcp?apikey=YOUR_API_KEY",
      "type": "streamableHttp"
    }
  }
}

Get your API key at Patsnap Open Platform.

Usage Example

  • Use Internal Patent Data Connector to search for the most relevant records for my topic.
  • Summarize the top results and cite the returned record names or IDs.
  • Compare the findings and suggest follow-up queries.

Related Links

License

Apache License 2.0 (see ../../LICENSE)

Powered by Patsnap. Innovate with Confidence.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.