Claude AdisInsight connectorWhat Claude can do in your AdisInsight account.
The Claude AdisInsight connector lists 7 tools. 4 read drug and trial records, 0 write anything, and 3 are named with no official description. Below: what Claude can look up, what stays unclear, and who in your company can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a pipeline or competitive intelligence analyst
Instead of building filters in the AdisInsight interface, you ask Claude in plain English. It searches Springer Nature's drug and clinical trial database with your own AdisInsight login, opens the profiles it needs, and writes the answer back into the conversation. Everything it reports comes from records you could already open yourself.
A pipeline snapshot in one question. You need every compound in phase 2 for a given indication: search_drugs filters by developer, mechanism, phase or target, and Springer Nature advertises 60+ advanced filters for it.
The full story of one molecule. A board member asks why a candidate stalled. get_drug returns its development history, reported adverse events and brand names, so Claude can summarize the record instead of you copying it out.
A trial shortlist for a site feasibility call. search_trials narrows trials by sponsor, status, location or patient demographics, then get_trial pulls the endpoints, eligibility criteria and study centres of the one that matters.
Now the part the directory sheet skips. Three of the seven listed tools have no official description at all, so this page does not say what they do. Springer Nature restricts the whole service to research: no treatment decisions, and no patient data typed into the chat. Nothing runs on its own either. Claude only calls these tools while it answers you; no alert fires when a trial changes status. If you want that kind of background watch, it is the job of an automation tool, a different line of work, and the Integrations hub is where that side lives.
Five words before you connect
The vocabulary you will meet while plugging AdisInsight into Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs mid-answer, 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, revocable later.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: the piece that lets an assistant like Claude talk to an outside service.
Connect AdisInsight to Claude in three steps
- 01
Find AdisInsight in Claude
In Claude's settings, open Customize, then Connectors, and look for AdisInsight in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first, before any member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to AdisInsight in the window the service opens itself. If the link ever breaks, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before you accept. It belongs to AdisInsight, not to Claude, and it sets what the access covers. You can also withdraw that access later from the service side.
The 7 tools, sorted by what they do
AdisInsight gives Claude 7 tools: 4 that read your account, 0 that change something in it, and 3 no official source describes.
Two groups here: what Claude reads, and what no official source describes. Tool names stay exactly as Claude shows them.
- 4 read
- 3 not documented
What Claude reads (4)
4 toolsFour tools that look up drug and trial records without changing anything.
search_drugs
Finds medicines in the database by name, indication, developer, mechanism of action, development phase or target, with dozens of finer filters on top. Claude gets back a list of matching drugs to work from.
get_drug
Opens the full record of a single drug: its development history, adverse events, the organizations involved and its brand names. That gives Claude the material to summarize one molecule in depth.
search_trials
Looks for clinical studies by condition, sponsor, compound, phase, status or location, and can also narrow on patient demographics and date ranges. Claude receives the studies that fit.
get_trial
Retrieves everything recorded about one study: investigators, study centres, compounds, indications, endpoints and eligibility criteria. Claude can then compare it against another trial or pull out a single detail.
Not documented (3)
3 toolsThe directory lists these three names and nothing else. No official text says what they do, so this page will not guess from a name.
search_drug_companies
This name appears in the directory's tool list, and that is all anyone has published. Springer Nature's setup page presents four other tools and never mentions this one.
search_trial_companies
Same silence for this second name: listed on the directory sheet, yet no source documents it, neither the publisher's page nor Claude's help center. Better to flag the gap than to fill it with a guess based on how the name sounds.
generate_chart
The directory description mentions interactive charts, but no sentence ties that capability to this tool by name, so this page keeps it in the undocumented group. No official text says what it does to your data, if anything.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before every action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked each time. They can also cap what a connector may do for the whole organization, for example keeping reads open and closing writes. That setting applies to everyone, and nobody overrides it from their own account. Claude also works with your AdisInsight rights and nothing more: a record your login cannot open stays closed.
Which plans it works on
Out of 819 sheets in the official directory, not one shows availability by plan. That answer, connector by connector, is published nowhere: it is a real gap in the catalog.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can connect. For the current state of this one, check the AdisInsight sheet in the official directory from your own account, through the button on this page.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a trial is registered, changes phase or reports results.
A tool list that only shows reads is an observed floor, not a promise: an admin can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. This connector is documented only by its publisher, Springer Nature; neither Claude's help center nor Anthropic's developer docs have a page for it. For a connector that actually writes, compare with the Claude activecampaign connector.
Need help connecting AdisInsight to Claude?
A person reads every message.