How to Connect Internal Patent Data to an AI Assistant
Connect Claude to Internal Patent Data Connector, a patent data connector built for internal systems and automated workflows, to search patents and pull transfer, licensing, and legal-status records for a specific result — without leaving the conversation.
Patent researchers, IP analysts, and R&D teams often need to move from a broad patent search to detailed legal and commercial records for specific documents. Claude can help refine the research question and organize findings, but it has no live connection to patent data on its own.
Internal Patent Data Connector closes that gap: it gives Claude access to unified patent search, legal status, transfer, licensing, pledge, and classification data through MCP (Model Context Protocol), functioning as an internal patent data API you can call repeatedly or embed into an automated pipeline. This tutorial walks through a live example: searching for a therapeutic target, retrieving the top result, then querying that patent for transfer and licensing records.
What Internal Patent Data Connector does
The connector gives Claude nine tools covering patent search, valuation, transfer data, licensing data, and technology classification, returning structured JSON that Claude parses and presents in natural language. That means you can ask Claude to search for patents matching a technical description, then immediately request transfer or licensing details for a specific result — without switching between separate systems or manually retrieving identifiers.
Prepare your search query
For this tutorial, the starting point is a therapeutic research question: finding patents related to semaglutide, a GLP-1 receptor agonist used in diabetes and weight management therapies. The query is a plain-language string — “semaglutide GLP-1 receptor agonist” — with no special patent query syntax required. Once you have a result, its identifier is what you’ll use for follow-up requests such as transfer records, license agreements, or legal status.
Connect Internal Patent Data Connector
Internal Patent Data Connector uses the Model Context Protocol to integrate with Claude Desktop and other compatible MCP clients.
https://connect.patsnap.com/cac75e/mcp?apikey=yourapikey Replace yourapikey with your own Patsnap Open Platform API key before connecting. Keep the completed URL private. - Get a Patsnap Open Platform API key.
- Copy the connection URL or JSON config from the Connect panel on the Internal Patent Data Connector page.
- Add the server to Claude Desktop or another MCP-compatible client.
- Restart or reconnect the client, then confirm the connector’s tools are available.
Search, then pull linked records
Use the connected Internal Patent Data Connector to search for patents related to "semaglutide GLP-1 receptor agonist." Return the top result with its publication number and assignee, then retrieve transfer data and license data for that same patent using its internal identifier.The search returned 10 patents on the first page, out of 12,594 matching documents. The top result was EP4721726A1, assigned to AULBIO CO., LTD. — the same top document Global Core Patent Database returns for the identical query, confirming both tools draw on the same underlying data.
The result carries an internal identifier (6662262e-f5af-4bf1-8d08-84eab1c7a47a) that the connector uses for follow-up lookups. The next two calls request transfer data and license data for that identifier, showing how a search result flows directly into linked commercial and legal records.
What the results tell you
| Returned field | What it tells you |
|---|---|
| Publication number (EP4721726A1) | Which document matched the query, and which authority published it |
| Assignee (AULBIO CO., LTD.) | The current recorded owner in the search index |
| Internal identifier | The key the connector uses to link this result to transfer, license, legal-status, and other record types |
Go further with follow-up questions
From the same identifier, you can ask Claude for the patent’s legal status, its technology classification, or a valuation check — each builds on the metadata already returned, in the same conversation. To widen the search, ask for the next page of results or add more specific technical terms to the original query.
Frequently asked questions
What is a patent data connector?
A patent data connector gives an AI client like Claude a live, structured connection to patent search, legal status, transfer, licensing, and classification data through MCP, instead of relying on the model’s static training data.
Why did the transfer and license lookups return no records?
No transfer or licensing record exists for that patent in the connected data set — this is a normal outcome, not an error in the query or connection.
Is this the same data as Global Core Patent Database?
Yes, same underlying database — Internal Patent Data Connector is scoped for system integration and automation, while Global Core Patent Database exposes a broader tool set for daily research.
Can Claude search patent data without a connector?
No. Claude can help frame the question and interpret results, but a tool like Internal Patent Data Connector supplies the live data connection through MCP.
Connect a patent data connector to Claude
Bring unified search, transfer, license, and legal-status data into your Claude workflow.
