MCP startup sues Rippling over its gateway
Runlayer accuses Rippling of copying its MCP gateway after a year of sales-trial collaboration under NDA; Rippling calls the suit a bid to dodge competition.
Runlayer, a startup that raised $42 million to build a secure Model Context Protocol gateway (infrastructure that lets AI models and agents safely reach external data and tools), filed suit against Rippling on July 28, alleging trade secret misappropriation, unfair competition, and breach of contract. According to the complaint, Runlayer shared its product roadmap and source code with Rippling during nearly a year of what it describes as intensive engineering collaboration, under a mutual NDA and a product-trial agreement that prohibited derivative works. After the two companies failed to agree on pricing and the trial ended, Runlayer says an insider told its CEO that Rippling’s own MCP gateway product was “almost a 1 to 1 copy of Runlayer.”
Rippling, the HR software company with a large in-house engineering organization, denies the allegations. In its response, Rippling says it is “launching a superior product…using only our proprietary information” and characterizes Runlayer’s lawsuit as a “panicked” attempt to avoid direct competition rather than a legitimate legal claim.
What it means for operators
MCP gateways are becoming standard infrastructure for any company connecting agents to internal systems, a category that’s only gotten more central since the protocol’s biggest spec rewrite shipped this week, which makes this dispute worth watching regardless of how it resolves legally. If you’re building or buying MCP infrastructure, the practical lesson is upstream of the lawsuit itself: any serious vendor evaluation involving a large potential customer with strong engineering resources carries real risk that the evaluation becomes a blueprint, intentionally or not. Whether Runlayer’s specific claims hold up in court, the pattern, a smaller vendor sharing deep technical detail during a sales cycle that ends without a deal, then discovering a near-identical competing product, is one worth protecting against contractually before you’re in the position of having to prove it after the fact. It’s also a reminder that MCP infrastructure disputes now carry real commercial stakes, not just the technical governance questions Mistral’s own MCP connector rules were built to answer.