Claude LatchBio connectorWhat Claude can do in your LatchBio account.
The Claude LatchBio connector exposes 9 tools. 8 of them read your Latch workspace (files, workflows, executions, logs) and 1 starts a workflow run. Below: what Claude can see, the one action it asks about first, and what a launch costs you.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Latch workspace
With the connector, you ask in plain words and Claude works in your Latch workspace: it lists folders, finds a pipeline, reads its parameters, starts a run once you agree, and reports back on status and logs, all inside the conversation. Latch presents it as a way to run serverless pipelines written in Nextflow or Python without leaving Claude.
Know what is in a folder before you touch it. Claude calls list_files to show what sits in a directory of Latch Data, then get_file to hand you a Console link or a temporary download link for the file you pick.
Go from "which pipeline?" to a run. list_workflows surfaces the workflows of your workspace plus public ones, get_workflow_schema shows which parameters a launch needs, and launch_workflow starts it with values that match that schema. Latch says Claude asks your permission before that launch by default.
Follow a run without opening the Console. list_executions and get_execution give status, task nodes and result files; get_task_logs brings the logs of a failing task into the chat.
What Claude will not do here: read the contents of a file through list_files (Latch says that tool returns names, not contents), edit or delete your data, or start anything on its own schedule. Every run you launch through Claude is billed like a run started from the Console. The connector also does not replace your Latch login: its sign-in only serves Claude, not the SDK. For other connectors documented the same way, the Integrations hub lists them.
Five words to know before connecting
Claude's vocabulary for this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, here Latch, so Claude can work in it while it answers you.
- Tool
- One named action the connector gives Claude, such as listing executions. Claude picks the ones it needs on its own while replying.
- Authorization
- Latch's own sign-in screen, where you grant the access Claude will use. It is given once per person and can be withdrawn later.
- Approval
- The confirmation Claude waits for before doing something that changes your account, such as starting a workflow run on Latch.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Latch.
Connect LatchBio to Claude in three steps
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and find LatchBio. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on first; after that, each member connects on their own.
- 02
Sign in to Latch
Click Connect on the LatchBio row. Latch opens its own window, where you log in with your Latch account. If the link breaks later, use Disconnect and connect again.
- 03
Approve the access screen
Read the authorization screen before you accept. It is Latch's screen, not Claude's, and it sets what the access covers. You can also withdraw that access later from the Latch side.
The 9 LatchBio tools, read versus write
LatchBio gives Claude 9 tools: 8 that read your account, 1 that change something in it.
Two groups: what Claude reads in your workspace, and the single tool that starts something. Names stay exactly as Claude displays them.
- 8 read
- 1 write
What Claude reads (8)
8 toolsEight tools that look at data, workflows and runs without changing them.
list_files
Shows the immediate contents of one directory in Latch Data, so you see the names of what sits there. It stops at that level and never returns what is inside the files.
get_file
Hands back a way to reach one stored file: either a link that opens it in the Latch Console or a presigned URL to download it directly.
list_workflows
Finds the workflows you could launch: the ones built in your own workspace and the public ones Latch makes available to everyone.
get_workflow_schema
Fetches the launch details of one workflow along with its parameter schema, which tells Claude what values a run expects before anything starts.
list_executions
Returns the workflow runs of a workspace, optionally narrowed by name, workflow or status, so Claude can spot failed or running jobs in one pass.
get_execution
Pulls the detail of one run: its status, its task nodes, the result files and a Console URL to open it in the browser.
get_task_logs
Brings in the logs of a task, either inline in the conversation or as a presigned URL when you want the complete file.
list_workspaces
Lists every workspace your account can reach, the default one included. It only reports which workspaces exist for you and leaves them as they are.
What Claude starts (1)
1 toolOne tool that launches a billed workflow run, with your permission asked first by default.
launch_workflow
Asks you firstStarts a run of a workflow with parameter values that match its schema. It is the only tool here that sets something in motion on Latch.
What Claude asks before acting
By default, Claude pauses and asks for confirmation before each action it carries out on an account for someone.
For LatchBio, the publisher spells it out for the one tool that matters: a workflow launch waits for your yes. On Team and Enterprise workspaces, owners decide whether a member may let some actions pass without a prompt each time, and they can limit what a connector does for the whole organization. Claude also uses your rights and nothing more: a workspace you cannot open on Latch stays closed to it.
Which plans can use it
No official source publishes plan availability connector by connector, and none of the 819 sheets in the directory shows it.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before members connect. For LatchBio's live state, check its sheet in the official directory. Separately, you need a Latch account.
Where the LatchBio connector stops
A connector is not an automation. Claude calls these tools while it answers you: no run starts by itself when new files land in Latch Data.
Everything known about this connector comes from its publisher: no Claude help page covers it. The partner badge is not a security audit, and Anthropic states it neither picks the tools a publisher exposes nor guarantees how they behave. The tool list is also a floor rather than a ceiling, since an administrator can open actions no public sheet shows. Anthropic's own advice on every sheet applies here too: only connect a publisher you know.
Need help connecting LatchBio to Claude?
A person reads every message.
