The emerging pattern: CLI + MCP. What RudderStack Inc. is seeing across teams is a clear architectural pattern: Write | Config + CLIRead | MCP This can be thought of simply as: state changes happen through the CLI, while system understanding happens through MCP. This separation isn't entirely new. It mirrors patterns in traditional infrastructure systems. But AI agents make it significantly more important. Agents are extremely good at generating structured outputs like configurations, schemas, and transformations, which makes them well-suited for config-driven write paths via CLI. At the same time, agents are inherently exploratory. They ask questions, iterate, and reason over intermediate results. This makes safe, read-only interfaces like MCP essential for enabling that behavior without risk. When these concerns are blurred, systems become harder to debug, risk unintended mutations, and lose operational control. When they are clearly separated, you get better safety, clarity, composability, and overall agent reliability. RudderStack was built for this model. CLI + config for state changes. With Rudder CLI and Terraform, you can define your entire data stack as code - covering sources, destinations, tracking plans, transformations, and pipelines. Everything is declarative, version-controlled, and reproducible. This also makes it a natural interface for AI agents: They generate configuration, humans validate it, and the CLI applies it. MCP for system introspection. On the read side, RudderStack Inc. has introduced MCP support. Its MCP interface allows agents to inspect pipeline state, configuration, event flows, and system metadata in a safe, read-only way. This enables agents to debug pipelines, analyze data quality issues, understand system behavior, and answer operational questions, without modifying anything. The bigger shift: AI as the control plane. What's emerging is not just a tooling shift, but an architectural one. Traditionally, the interface to a data platform looked like: UI | API | Infrastructure Now it increasingly looks like: Agent | (CLI + MCP) | Infrastructure The agent becomes the control plane. Humans express intent in natural language. Agents translate that intent into configurations and queries. Infrastructure executes those actions deterministically. This changes how systems need to be designed. The best systems for this world will expose structured configuration for writes, clear CLI workflows for execution, and safe read-only interfaces for reasoning. Final thoughts. RudderStack Inc. is still early in this transition. But one thing is already clear: AI agents are not just assisting with infrastructure. They are becoming the primary way it is operated. And in that world, the question is no longer: CLI or MCP? It's: How well does your system separate and support both? Published: March 18, 2026

RudderStack has launched infrastructure-as-code driven governance capabilities for its customer data infrastructure, positioning itself as a "customer context engine for the AI era". The new features help teams operationalise AI with fresh, trustworthy customer context whilst maintaining data ownership and compliance. The company delivered 3.3 trillion events for over 4,000 organisations in 2025, with rapidly growing adoption among AI-native companies including AssemblyAI, Otter.ai, and Replicate. RudderStack's warehouse-native architecture makes customers' existing data warehouses the system of record for consistent customer context at scale. The new IaC capabilities enable teams to define events and schema rules in version-controlled configuration files, with automated validation to catch issues before impacting production. RudderStack also released performance enhancements to its Profiles product, accelerating customer context creation and updates.