Overview
The Model Context Protocol (MCP) is an open standard for connecting AI applications to external systems. You can use Latch’s remote MCP server to securely connect your favorite AI development tools to the Latch platform. You can then directly access Latch resources and carry out actions on the Latch platform. Using the Latch MCP requires you to have a Latch account. While there is no separate pricing for the MCP, you will be charged normally for any actions you perform on Latch using the MCP. For example, if you use the MCP to launch a Latch workflow, you will be charged the same as if you had launched it directly from the Latch Console or SDK.Setup
The best way to use the Latch MCP right now is as a connector in Claude (web) or Claude Desktop. We plan to roll out support for other development tools (Codex, Claude Code, VS Code, etc.) soon. Follow the steps in Claude’s documentation to set up a third-party connector. When asked to provide the remote MCP URL, usehttps://mcp.latch.bio/mcp. Once you have set up the connector, you will be asked to authorize the connector to access your Latch account.
Tools
The Latch MCP server exposes tools that allow an AI agent to interact with the Latch platform. By default, Claude will ask you for permission before launching workflow executions.| Tool | Description |
|---|---|
list_files | Lists the immediate contents of a directory in Latch Data. File contents are not returned. |
get_file | Returns access information for a file stored in Latch Data, either as a Latch Console link or as a presigned download URL. |
list_workspaces | Lists the workspaces the current user can access, including the default workspace. |
list_workflows | Discovers workspace workflows and public workflows that can be launched. |
get_workflow_schema | Fetches launch metadata and parameter schema for a workflow. |
launch_workflow | Launches a workflow with parameter values matching the workflow schema. |
list_executions | Lists workflow executions in a workspace, with optional filters for name, workflow, and status. |
get_execution | Fetches workflow execution status, task nodes, result files, and a Console URL. |
get_task_logs | Fetches inline task logs or a presigned download URL for full task logs. |