LatchBio

Browse bioinformatics data, launch Nextflow and Python workflows, monitor executions.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the LatchBio connector does

The LatchBio MCP server connects a Latch workspace — a cloud bioinformatics platform for sequencing data and pipelines — to Claude, ChatGPT and any MCP-compatible agent. Nine tools browse files, discover workflows, launch Nextflow or Python pipelines, and monitor executions. Sign-in is OAuth. One tool spends real money.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

LatchBio tools (9)

  • list_files
  • get_file
  • list_workflows
  • get_workflow_schema
  • launch_workflow
  • list_executions
  • get_execution
  • get_task_logs
  • list_workspaces

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • One tool spends money, and no scope prevents it. launch_workflow bills your workspace at published Latch rates. The only controls are your MCP client's approval prompt and your Latch workspace role — not the OAuth grant, which draws no line between reading and launching.
  • Nothing stops, cancels or deletes. The nine tools cannot cancel a running execution, delete a file, or remove a workflow. A run started through the connector must be stopped from the Latch Console or SDK. That asymmetry cuts both ways: it limits blast radius, and it means the agent cannot clean up after itself.
  • No plan gate, but a billing prerequisite. LatchBio charges no MCP-specific fee, and its pricing model has no subscription or per-seat charge. But launching anything requires credits, so a workspace without a payment method can browse and monitor and not much else.
  • Public workflows are not vetted. list_workflows surfaces community-built workflows alongside Latch Verified ones, and LatchBio states community workflows are not actively vetted. An agent choosing from that list is choosing which container to run on your data.
  • Presigned URLs land in your transcript. get_file and get_task_logs can return download URLs that work for anyone holding them. LatchBio does not publish their expiry, and we did not test it. Treat them as live credentials of unknown lifetime.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail — including what launch_workflow accepts, or whether it can request a specific instance size — is published here.
  • No published MCP rate limits. LatchBio documents no rate limits for the MCP server, and we did not probe for them. Absence of documentation is not absence of limits.
  • Your data leaves Latch's guarantees when a tool returns. LatchBio commits not to train models on your data and holds SOC 2 Type II. Neither commitment follows a tool result into your AI provider's context. For human genomic or clinical data, that is the decision to make before connecting.
  • trust.latch.bio was not readable. LatchBio's security page directs readers to its Trust Center for its 50-plus safeguards; that host returned 403 to our request on 2026-08-22, so the compliance claims cited here come from LatchBio's own FAQ and marketing pages rather than from audit artefacts we read.

Frequently asked questions

Does launching a LatchBio workflow through the MCP server cost money?

Yes, at the same rates as launching it yourself. LatchBio's docs state you are charged normally for any action performed through the MCP, the same as from the Console or SDK. Its pricing page sets 1 credit at 1 US dollar and gives a worked bulk RNA-seq run at 14.101 credits for 18 minutes.

Can Claude launch a bioinformatics workflow without asking me?

LatchBio states that by default Claude will ask permission before launching workflow executions. That default lives in your MCP client, not in the server, so it is a client setting you can change rather than a server-side block. Treat approval as the control and keep it on.

What OAuth permissions does the LatchBio MCP server request?

Only identity ones. The server's RFC 9728 descriptor declared scopes_supported of openid and offline_access on 2026-08-22, which identify you and keep the session alive. Neither narrows anything. No scope separates listing a file from launching a workflow that spends credits, so consent is all-or-nothing.

Can the LatchBio connector read human genomic or patient data?

Yes, if your workspace holds it. Latch Data stores FASTQ, BAM and single-cell files, and LatchBio's own documentation works through examples using human patient cohorts. Whatever a tool returns enters your AI client's context, so the connector's read reach is exactly your workspace's data, not a filtered subset.

Does the LatchBio MCP server let an agent download my files?

Effectively yes. The get_file tool returns access information as either a Latch Console link or a presigned download URL, and get_task_logs can also return one. A presigned URL is a bearer credential — anyone holding the string can fetch the file without signing in to Latch.

Can the connector delete data or cancel a running execution?

No. None of the nine tools carries a delete, remove, cancel, abort or stop verb, and LatchBio's own tool table describes none. The surface writes in exactly one direction: launch_workflow starts new work. Stopping or deleting anything still requires the Latch Console or SDK.

Is LatchBio SOC 2 compliant?

Yes. LatchBio's FAQ states the company is SOC 2 Type II compliant following a three-month independent audit that included penetration tests. Its security page adds annual penetration tests, AES-256 encryption at rest and in transit via AWS KMS, and role-based workspace access assigned by administrators.

Which AI clients work with the LatchBio MCP server?

LatchBio documents four by name: Claude web and Desktop as a third-party connector, Claude Code, Codex and Cursor, each over OAuth at the same URL. Anthropic's directory lists compatibility with Claude, the Claude API and Claude Code. Any other MCP client can use the same endpoint.

Sources

More Healthcare connectors

  • AdisInsight

    Query Springer Nature's drug-pipeline and trial database from an AI agent.

  • AdvancedMD

    Look up patients, find open slots, book appointments, and work denials and remittances in AdvancedMD from your AI agent.

  • AllTrails

    Search AllTrails' trails by place, map bounds or name and pull details and a 7-day trailhead forecast from your AI…

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put LatchBio to work.

Connect LatchBio once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio