Integrations on Kubemoot

The Crew Liaison

Mon, 01 Jan 0001 00:00:00 +0000

A crew is a committee. From inside the cluster you can watch it work: agents convening, findings arriving, signals settling. From outside, a client should not have to. The crew liaison is the operator’s door for other agents: one MCP endpoint that fronts every crew in the cluster, takes a question, and hands back the crew’s synthesized answer.

What the client sees

Three tools, and nothing about the discussion’s substance.

Claude Code

Mon, 01 Jan 0001 00:00:00 +0000

Claude Code speaks MCP over HTTP natively, so connecting it to the crew liaison is one command. See The Crew Liaison for what the tools do and why the answer comes by ticket.

Try it against any cluster you can reach

Port-forward the liaison’s Service and add it as a local server:

kubectl -n kubemoot port-forward svc/kubemoot-operator-liaison 18080:80
claude mcp add --transport http kubemoot http://localhost:18080/mcp

Start a new Claude Code session and ask in plain language:

Claude Desktop

Mon, 01 Jan 0001 00:00:00 +0000

Claude Desktop connects to remote MCP servers through its connector settings, with OAuth or no authentication, and cannot add custom headers. The crew liaison is usually behind a bearer token or an access gateway, so Desktop reaches it through mcp-remote, a small bridge that runs locally, speaks stdio to Desktop, and forwards to the liaison with whatever headers it needs.

Configuration

Add the liaison to claude_desktop_config.json (Settings, Developer, Edit Config):