- Home
- Resources
- Integrations
- Synthesize Bio
Claude Synthesize Bio connectorWhat Claude can do in your Synthesize Bio account.
The Claude Synthesize Bio connector exposes 6 tools: 3 in read, 1 in write and 2 left undocumented. Claude turns a plain experiment description into sample groups, starts a gene expression analysis once you confirm them, follows the run and fetches the results.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can drive Synthesize Bio
Instead of setting up groups and parameters in a platform, you describe the comparison you have in mind, such as tumour against normal lung tissue, and Claude handles the steps. It resolves your wording into sample groups, starts the analysis on your Synthesize Bio account after you confirm them, waits for the run and brings back the report, all inside one conversation.
From a sentence to defined groups. Claude first calls resolve_sample_metadata, which converts your description into structured sample groups and flags anything it could not match, such as a misspelt compound.
Running the comparison. Once you have confirmed the groups, analyze_gene_expression starts the differential expression pipeline. Synthesize Bio says most runs take about 3 to 5 minutes, so Claude keeps checking with get_analysis_results until the report is ready.
Taking the data elsewhere. When you want the raw counts for your own scripts, get_counts_data_url returns a download link instead of pouring a large file into the chat.
What it will not do: a run compares two groups only, and if your prompt implies more, the first two in alphabetical order are used. Two tools on the directory sheet are not described anywhere. And nothing starts on its own: Claude acts only while it answers you. The Claude connectors hub lists other life-science connectors, and the Integrations page covers automation platforms.
Five words before you connect
The Claude vocabulary behind this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do on that account. Claude picks the tools it needs, and the directory sheet lists them by name.
- Authorization
- The Synthesize Bio sign-in screen where you hand Claude the access it will use afterwards. Granted once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors rely on: it is what lets an assistant such as Claude talk to an outside service like Synthesize Bio.
Connecting Synthesize Bio to Claude in three steps
- 01
Find Synthesize Bio in Claude
Open Claude's settings, go to Customize then Connectors, and search for Synthesize Bio. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first so members can sign in individually.
- 02
Start the connection
Click Connect on its row, then sign in with your Synthesize Bio account in the window the service opens. The publisher says no separate account is needed for the connector. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before you accept. It belongs to Synthesize Bio, not to Claude, and it decides what the access covers. You can remove that access later from your Synthesize Bio account as well.
The 6 Synthesize Bio tools, sorted by what they do
Synthesize Bio gives Claude 6 tools: 3 that read your account, 1 that change something in it, and 2 no official source describes.
Synthesize Bio documents four of these tools; two appear on the directory sheet with no description. Names stay as Claude shows them.
- 3 read
- 1 write
- 2 not documented
What Claude reads (3)
3 toolsThree tools that resolve, follow and fetch, without starting anything new.
resolve_sample_metadata
Turns a plain-language experiment description into structured sample groups ready for analysis, and returns warnings when something such as a drug or compound is not found in its reference ontology.
get_analysis_results
Polls a running analysis and reports its stage, from the model inference to the statistical comparison, then returns the result once done. Each call waits on the server for up to roughly 40 seconds.
get_counts_data_url
Returns a temporary download link for the raw gene expression counts produced by a finished analysis, so the data can be processed outside the conversation.
What Claude starts (1)
1 toolOne tool that launches an analysis job on your account, after the groups are confirmed.
analyze_gene_expression
Asks you firstStarts the differential gene expression pipeline on your Synthesize Bio account from a resolution you have confirmed, comparing the two sample groups in bulk or single-cell mode.
Not documented (2)
2 toolsListed by name on the directory sheet, described by no official source. This page says nothing more about them.
get_saved_analysis_report
Synthesize Bio's tool reference documents four tools and this one is not among them; the directory sheet shows its name and nothing else. No official source states what it returns, so this page does not guess. The general approval rule of the block below applies to it like to any call.
annotate_genes
Absent from the publisher's tool reference, this one is published by the directory as a bare name, with no sentence describing it. Without any documentation, nothing can be said here about what it reads or produces. If Claude calls it, the default approval rule set out further down is what covers that call.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account in your place. Here, Synthesize Bio adds its own checkpoint before an analysis starts.
The publisher requires the resolved sample groups to be confirmed before an analysis is launched, which gives you a natural moment to check them. On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked again, and they can bound what any connector may do for the whole organisation; nobody overrides that from their own account. Claude works with your rights and no more: what your Synthesize Bio account cannot reach, Claude cannot reach either.
Which plans include it
None of the 819 sheets in the official directory displays availability by plan. Connector by connector, the answer is published nowhere: it is a real gap in the catalogue.
What is published is the general rule: 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 organisation before each member signs in. For the current state of this one, check its sheet in the official directory. Note that only Synthesize Bio documents it; no Claude help article covers it.
Where the Claude Synthesize Bio connector stops
A connector is not an automation. Claude calls these tools while it answers you: no analysis starts on a schedule or when a new file lands somewhere.
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 says on every sheet that it does not choose the tools a publisher exposes and cannot guarantee they behave as announced. Connect only what comes from a publisher you trust, here Synthesize Bio, whose documentation is the only one describing this connector.
Need help connecting Synthesize Bio to Claude?
A person reads every message.