- Home
- Resources
- Integrations
- Amass Connector
Claude Amass connectorWhat Claude can do in your Amass account.
The Claude Amass connector exposes 14 tools. 13 search and read life science records, 1 files a data report with the Amass team, and 0 are left undocumented. Below: the six linked databases, what each tool returns, and where the limits sit.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can query Amass
Amass gathers biomedical records into six linked databases it calls Cores: publications, clinical trials, regulatory approvals, drugs, genes and patents. With the connector, Claude searches them while it answers you, opens the records that matter, and every result carries a link back to its source, so you can check each claim instead of trusting a summary.
Map a trial landscape. A business development analyst asks which late-stage trials target one mechanism: search_amass_trialcore_records filters by phase and recruitment status, across US and non-US registries, and get_amass_trialcore_record opens the ones worth reading.
Compare two labels. A regulatory affairs lead pulls an FDA approval and its EMA counterpart with search_amass_regulatorycore_records, then reads the exact section that differs through get_amass_regulatorycore_document_section.
Check a target before betting on it. A research team filters genes by druggability with search_amass_genecore_records, then follows the links to the drugs, trials and papers attached to the record.
What it will not do: write to the databases, edit a record, or search the open web. The one tool that sends anything, send_feedback, only files a report with the Amass data team. Nothing runs by itself either, such as an alert when a new trial is registered; Claude acts only while it answers you. The Integrations hub lists the other apps we cover.
Five words to know first
The vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work with it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the tools it needs by itself, and the directory lists them by name.
- Authorization
- The Amass sign-in screen where you hand Claude the access it will use afterward. Given once per person, and you can revoke it.
- Approval
- The confirmation Claude waits for before it does something that changes or sends data, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Amass.
Connect Amass to Claude in three steps
- 01
Find Amass in Claude
Open Claude's settings, go to Customize then Connectors, and look for Amass. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Sign in to Amass
Click Connect on its row, then sign in to Amass in the window that the service opens itself. Amass says you sign in once and no API key is needed. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read the Amass authorization screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. You can withdraw that access later from the same connector list.
The 14 tools, split by what they do
Amass Connector gives Claude 14 tools: 13 that read your account, 1 that change something in it.
Each of the six Cores has a search tool and a record tool, plus one tool for regulatory sections and one for feedback. Amass describes all of them in its changelog. Names stay exactly as Claude shows them.
- 13 read
- 1 write
Tools index
- get_amass_biomedcore_record
- get_amass_drugcore_record
- get_amass_genecore_record
- get_amass_patentcore_record
- get_amass_regulatorycore_document_section
- get_amass_regulatorycore_record
- get_amass_trialcore_record
- search_amass_biomedcore_records
- search_amass_drugcore_records
- search_amass_genecore_records
- search_amass_patentcore_records
- search_amass_regulatorycore_records
- search_amass_trialcore_records
What Claude reads (13)
13 toolsThirteen tools that search or open records in the six Cores, without changing them.
get_amass_biomedcore_record
Opens one publication from PubMed and PubMed Central with its abstract and, when you ask for it, the full text.
get_amass_drugcore_record
Brings back one drug or molecule with its trade names, synonyms, modality, clinical stage and chemical structure, plus how it acts on each target and which genes it hits.
get_amass_genecore_record
Fetches a human gene record: approved symbol, name, synonyms, gene family and type, functional summary, genomic location, external identifiers and protein annotations.
get_amass_patentcore_record
Looks up a patent directly by its publication number or Amass identifier and returns its bibliographic data, full text, classifications, inventors, assignees, key dates and citation lineage.
get_amass_regulatorycore_document_section
Pulls the full text of a single section of a regulatory document: an FDA label or review, an EMA product summary or assessment report.
get_amass_regulatorycore_record
Opens one regulatory record, from an FDA NDA or BLA approval to an EMA marketing authorization, on the shared schema Amass uses for both agencies.
get_amass_trialcore_record
Retrieves a single clinical trial. It accepts an Amass ID, an NCT ID or a native registry ID, so non-US trials can be fetched too.
search_amass_biomedcore_records
Searches the publications Core, abstracts included, with filters for publication date, journal quality, retraction status and author or institution.
search_amass_drugcore_records
Finds drugs and molecules by name or synonym and narrows them by modality and clinical stage, returning harmonized records you can open one by one.
search_amass_genecore_records
Searches harmonized human gene records with filters such as gene type or biotype, druggability, CRISPR essentiality, ChEMBL target class, clinical-precedent tractability by modality and stage, curated safety liabilities and gnomAD genetic constraint.
search_amass_patentcore_records
Runs a full-text search over patents, which come with their classifications, inventors, assignees, key dates and citation lineage. Each patent family is collapsed into one result, so an invention filed in many countries takes a single slot.
search_amass_regulatorycore_records
Looks across FDA and EMA records together, filtering by agency, molecule type, authorization status, authorization date and orphan designation. The search covers both agencies unless you narrow it.
search_amass_trialcore_records
Queries clinical trials from ClinicalTrials.gov and national registries gathered through the WHO, filtering by phase, recruitment status, study type, intervention type, start date and posted results.
What Claude sends (1)
1 toolOne tool that files a data report with the Amass team. No source describes a confirmation for it, so the general rule below applies.
send_feedback
Approval: see the ruleFiles a report with the Amass data team about a wrong, missing or outdated value, a search that missed records that clearly exist, or a gap in the data model, and returns a receipt number.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone. The prompt shows up in the conversation at the moment it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without a prompt each time. They can also cap what a connector does for the whole organization, for example keeping the searches open and blocking the feedback tool, and nobody gets around that from a personal account. Claude works with the rights of the person who connected. Amass adds that it only sees the queries Claude sends and the answers it returns, and that the assistant runs on your provider's infrastructure, not on Amass's.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that answer is published nowhere by Anthropic.
The general rule is what 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 opens a connector for the organization before members can each connect. Amass's own page says something narrower; that contradiction is spelled out in the limits below. For the live state, check the Amass sheet in the official directory. Only Amass documents this connector; no Claude help page covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing alerts you when a trial is registered or a label changes.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge in the directory is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees they behave as announced. Connect what comes from a publisher you trust. For a connector built around business records rather than science, compare with the Claude affinity connector page.
Which Claude plans can use the Amass connector?
- Claude Help Center, general connector rule ↗2026-09-18Remote 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 first.
- Amass's own MCP page (FAQ) ↗2026-09The publisher lists Claude availability as Pro, Max, Team and Enterprise, in the connector directory.
What this page followsAnthropic's rule covers every connector; Amass's FAQ is the only sentence aimed at this one, but it is the publisher speaking, not Anthropic. Neither is authoritative for your own account: check the Amass sheet in the directory while signed in.
Need help connecting Amass Connector to Claude?
A person reads every message.