Connect an MCP client

Start the bridge from the same machine as your MCP client:

hyperlake mcp serve --stdio

The process speaks MCP over stdin/stdout. Do not print banners or diagnostics to stdout; MCP clients need that stream for protocol messages. Logs belong on stderr.

Configure the client to launch the command. A generic configuration looks like this:

{
  "mcpServers": {
    "hyperlake": {
      "command": "hyperlake",
      "args": ["mcp", "serve", "--stdio"]
    }
  }
}

The client sees only the tools exposed by the authenticated Hyperlake session. Typical workflows include listing clusters, discovering catalogs, running an authorized query, inspecting observability data, checking policy sync, and retrieving approved artifacts.

Local execution

The stdio process is local. Data requests are routed through the Hyperlake CLI’s authorized target path; query data is not uploaded to Hyperlake merely because an MCP client is being used.