- Home
- Resources
- Integrations
- Patlytics
Claude Patlytics connectorWhat Claude can do in your Patlytics account.
The Claude Patlytics connector exposes 5 tools, all of them read tools. 5 look up patents, papers or your vault, 0 write, 0 are undocumented. Below: what Claude can find, what stays in the Patlytics app, and who holds the switch.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your patent team
You describe an invention in plain language and Claude looks for the closest patents through Patlytics. The search is semantic: it works on concepts across patent claims, not on matching keywords. Patlytics says a richer description, covering how the invention works, the problem it solves and its components, brings back better results.
Map the prior art around an idea. From a description of a technical concept, find_similar_patents returns the patents whose claims come closest in substance, and it can be anchored on a reference patent.
Read a patent's claims in the conversation. With a publication number, get_patent brings back the patent's bibliographic data and its claims.
Look beyond patents and into your own holdings. search_npl covers academic papers, journals, conference proceedings and books through OpenAlex, while list_portfolios and list_vault_patents show the portfolios and private patents your organization keeps in Patlytics.
What Claude won't do here: no freedom-to-operate opinion, no infringement or invalidity claim chart, no drafting. Patlytics keeps that work in its web app and links to it from every result. Nothing runs in the background either, so no alert fires when a competitor publishes. That kind of watch belongs to an automation tool, which is a different job; the Integrations hub covers that side.
The vocabulary in one minute
Five terms you'll run into while connecting Patlytics.
- Connector
- The link you set up once between Claude and an account you already have, so it can work there while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself, and the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and revoked the same way.
- Approval
- The confirmation Claude waits for before something that changes an account goes through, shown in the chat right when it matters.
- MCP
- The shared standard under every connector: it's what lets an assistant like Claude talk to an outside service.
Connect Patlytics to Claude in three steps
- 01
Find Patlytics in Claude
Open Claude's settings, go to Customize, then Connectors, and look for Patlytics in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Hit Connect on its row, then sign in with your own Patlytics account in the window Patlytics opens. If the link ever breaks, use Disconnect and connect again.
- 03
Read the authorization screen
Read that screen before you accept. It belongs to Patlytics, not to Claude, and it sets how far the access goes. You can also pull that access back later from your Patlytics account.
The 5 tools, grouped by what they do
Patlytics gives Claude 5 tools: 5 that read your account, 0 that change something in it.
Just one group this time: all five tools look things up, none of them changes anything. Names stay exactly as Claude shows them.
- 5 read
What Claude reads (5)
5 toolsFive tools that look up patents, literature and your vault without touching them.
find_similar_patents
Takes a description of a technical concept and returns patents that match it at the level of ideas, compared against their claims rather than their wording. A reference patent number can be passed as an optional anchor for the search.
get_patent
Fetches one specific patent from its publication number and returns its bibliographic data along with its claims. It's the step that turns a number cited somewhere into the actual text of the claims, inside the conversation.
list_portfolios
Lists the patent portfolios, the workspaces your organization keeps in Patlytics. Only portfolios private to your organization come back, each with an id that list_vault_patents accepts to show the patents inside it.
list_vault_patents
Lists the private patents your organization has saved or uploaded to its Patlytics vault, unpublished drafts included. The listing can cover the whole vault or be narrowed to a single portfolio.
search_npl
Searches non-patent literature on a topic or a set of keywords: academic papers, journals, conference proceedings and books. Patlytics runs these searches through OpenAlex rather than through its own patent data.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the chat, right when it matters.
Here the publisher describes all five tools as lookups, and no source mentions a confirmation specific to any of them. On a Team or Enterprise workspace, Owners decide whether members may let some actions through without being asked each time, and they can limit what the connector may do across the whole organization. That setting applies to everyone, and nobody overrides it from their own account. Claude also works with your permissions and nothing more: a portfolio your Patlytics login can't see stays closed to it.
Which plans it's available on
None of the 819 sheets in the official directory shows plan availability. The per-connector answer isn't published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner first enables the connector for the organization. For the current state, check the Patlytics sheet in the official directory from your own account.
Where this connector stops
A connector isn't an automation. Claude calls these tools while it answers you, so no search reruns by itself when a new patent publishes.
By default, the directory sheet only exposes read tools, and Patlytics says the same. That's an observed floor, not a guarantee: an admin can open actions that appear on no public sheet. This connector is documented by its publisher alone, with no Anthropic page of its own. The rest of the family sits on the Claude connectors hub. The directory badge isn't a security audit either: Anthropic doesn't pick the tools a publisher exposes or vouch for how they behave.
Need help connecting Patlytics to Claude?
A person reads every message.