@subzero-labs/latch-mcp-server

Latch MCP server. Exposes Latch's policy engine as tools any MCP-compatible client (Claude Desktop, Cursor, Claude Code, Hermes via mcporter, etc.) can use.

Use it from an MCP client

Drop this into the client's MCP config — claude_desktop_config.json for Claude Desktop, .cursor/mcp.json for Cursor, etc.:

{
  "mcpServers": {
    "latch": {
      "command": "npx",
      "args": ["-y", "@subzero-labs/latch-mcp-server"],
      "env": {
        "LATCH_URL": "https://latch-beta.rialo.io",
        "LATCH_TOKEN": "lat_…",
        "LATCH_LINK": "lnk_…"
      }
    }
  }
}

Restart the client. The Latch tools (latch_authorize etc.) appear in the client's tool list.

Optional: hardware-bound agent identity

If you've enrolled this Mac via LatchSetup.app and want every Latch call signed by the Mac's Secure Enclave key, set one more env var:

"env": {
  "LATCH_URL": "https://latch-beta.rialo.io",
  "LATCH_TOKEN": "lat_…",
  "LATCH_LINK": "lnk_…",
  "LATCH_AGENT_IDENTITY_BIN": "~/Library/Application Support/Latch/bin/latch-agent-identity"
}

The MCP server spawns the bundled CLI to sign each request. See Latch's Devices page for the end-to-end walkthrough.

License

Apache-2.0