Starling-EX · Kubernetes ops via MCP

One command. Your cluster. Agent-ready.

Starling-EX gives your team and your AI agents a safe way to operate Kubernetes. It's a self-hosted platform with SSO, an operator, a Helm chart, and an MCP server and CLI. It runs in your cluster, under your control.

Stable version readyCommunity Edition: Apache-2.0Integrations in development
The problem

Simple cluster questions still need five dashboards

"Why is this pod restarting?" and "which services have no network policy?" still need kubectl skills and five dashboards. Giving an AI agent direct cluster credentials is a security review you'd rather not have.

8
observability technologies in use per organization on average
Grafana Labs, 2025
51%
of tech leaders report an AI skills shortage
Nash Squared, 2025
LLM01
Prompt injection is the top OWASP LLM risk for 2025; no single control fully prevents it
OWASP, 2025
How it works

Install, sign in, connect, ask

01

Install

Starling-EX into your cluster with the installer or the Helm chart.

02

Sign in

Through Dex SSO, federated to the identity provider you already use.

03

Connect agents

To the Starling MCP server, or use the Starling CLI from a terminal.

04

Ask in plain words

Agents get structured, scoped tools instead of raw kubeconfig access, and every call is auditable.

Key features

Built for agents that need guardrails

  • MCP server and CLI so agents can operate Kubernetes safely
  • Read-only by default for local MCP; write tools only when you explicitly enable them
  • Dex SSO, a Kubernetes operator and a Helm chart (Starling-EX Community Edition, Apache-2.0)
  • Runs in your cluster: your RBAC credentials and workload data stay in your environment
  • Feeds Reflexion: the same scoped access Reflexion uses to diagnose incidents
  • External features and integrations: in development
Who it's for

Platform teams adopting AI agents

  • Platform engineers who want one install for SSO, the operator and agent access
  • Teams adopting AI coding agents and MCP clients that need cluster access without broad credentials
  • Teams on a Murmuration tier putting their included Starling credits to work
Pricing

Credits, not seats

  • Starling credits are included with every Murmuration tier: 5,000 (Niche), 25,000 (Growth), 75,000 (Scale Partner), custom (Enterprise).
  • Top-ups: $1 = 50 credits.
  • Community Edition: Apache-2.0.
  • Starling-EX plan pricing: talk to us.
Status: Starling-EX is beta tested and the stable version is ready. Starling CLI v0.1.0 binaries are published on GitHub.
FAQ

Questions

What's the difference between Starling and Starling-EX?

Starling is the MCP server and CLI. Starling-EX is the self-hosted platform around it, with SSO, an operator and a Helm chart.

Can an agent break my cluster through Starling?

Local MCP runs read-only by default. Write tools are only exposed when you explicitly enable them, and calls are audited.

What do credits pay for?

Metered Starling tool calls. Murmuration tiers include a fixed credit grant, and top-ups are $1 = 50 credits.

Is it open source?

The Community Edition is Apache-2.0. The source repo isn't public yet.

Ask your cluster something in five minutes.

Get the Starling CLI