Latch MCP: Agent-Native Data Infrastructure
Access the Latch platform using Claude Code, Codex, or any agent
AI for biology requires agent-native infrastructure: systems where agents can store, process, and visualize large molecular datasets from the interfaces scientists already use. Biological tasks downstream of large spatial, single-cell, or proteomics assays require agents to dispatch bioinformatics tool calls and interleave results with text and plots in a chat interface.
These tools often require substantial computing resources, so deployments must be reliable, especially as data volumes from modern assays increase. Workflow time and cost can quickly inflate from retries and incorrect results, especially from tool calls that take hours to days. They should also be curated with appropriate parameters and agent-readable documentation, ideally provided by the original assay developer, to facilitate correct use across many complex scientific contexts.
At Latch, we’ve seen customers of our Solution Provider partners, like TakaraBio, Vizgen, and AtlasXOmics, use both the Latch Agent and external harnesses like Claude Code or Cursor to accelerate analysis of their data. While Latch users can already use our SDK to programmatically interact with the platform, this limits interaction to desktop environments with a configured shell environment.
Today we’re launching the Latch MCP, a remote MCP server that allows you to securely connect your favorite agent harness to the Latch platform and leverage verified bioinformatics tools built and maintained by kit and machine providers. Agents can navigate data on the Latch platform and launch existing deployments of validated bioinformatics workflows to analyze data.
The Latch MCP is also available via the Claude connectors directory - an Anthropic-verified and reviewed catalog of MCP servers - allowing you to use the Latch MCP across all Claude products, including Claude Science, Anthropic’s newly launched AI workbench for scientists.
Using the Latch MCP
To showcase how scientists can use the Latch MCP, we’ll walk through an example: analyzing a Takara Trekker experiment to study spatial patterning in the mouse brain. Trekker enables true single-cell spatial mapping by directly diffusing spatial barcodes to individual cell nuclei, eliminating the need for post-processing to resolve cellular identities.
A single experiment can generate several gigabytes of data per sample. As the number of samples grows, that quickly outpaces the limits of a scientist’s personal computer. Further, configuring a bioinformatics pipeline to take raw sample FASTQs all the way to a cleaned h5AD is no trivial task. With the Latch MCP server in Claude, scientists can simply point to their dataset and ask in plain language: “Launch the Trekker pipeline workflow on my mouse U_C dataset.” Claude can then access preconfigured, gold-standard pipelines published on Latch by Takara’s bioinformaticians and launch the workflow directly. Scientists can follow the Latch Workflow link to monitor progress or ask Claude to track the workflow status itself.
Once the pipeline finishes, scientists can then continue analysis using the Latch Agent. For example, the above video showcases using the h5AD viewer embedded in Latch Agent to visualize a larger Trekker mouse brain dataset. Alternatively, scientists can ask Claude to carry out further downstream analyses. Claude can access Latch Data, a cloud-based filesystem, to find the relevant result files. From there, Claude or any other agent can draw upon a rich library of verified spatial workflows:
NVIDIA RAPIDS for GPU-accelerated preprocessing
Cell2location or RCTD for cell-type deconvolution
BANKSY for spatial clustering
And more
Try It
You can now use the Latch MCP with any AI agent that supports MCP integration (setup instructions here).