Rippling Counter-Sues MCP Startup Runlayer, Escalating the First IP Litigation Over Model Context Protocol

Rippling filed a patent infringement lawsuit against MCP gateway startup Runlayer on August 10, 2026, accusing the smaller company of infringing three of its patents. The filing escalates a legal dispute that began two weeks earlier, when Runlayer sued Rippling in the U.S. District Court for the Southern District of New York alleging trade secret theft and breach of contract (TechCrunch).

Runlayer's original complaint, filed July 28, 2026, accuses Rippling of stealing its product ideas to build a competing MCP server (Reuters). The suit is described as the first intellectual property litigation involving MCP, the Model Context Protocol (Yahoo Finance). MCP is an open standard that allows AI agents to connect with data and software systems needed to work independently.

Runlayer, an NYC-based startup backed by Vinod Khosla, has raised a total of $42 million. The company launched its product roughly a year before the August 2026 filing. It bundles an MCP gateway with cybersecurity features such as threat detection. Founder Andrew Berman is a third-time founder; his previous companies were baby-monitor maker Nanit and AI video conferencing tool Vowel, which sold to Zapier in 2024 (TechCrunch).

The relationship between the two companies began as a commercial evaluation. Rippling spent nearly a year testing Runlayer's MCP product, but the two sides failed to agree on a price and the trial never converted to a paid contract (TechCrunch). Rippling subsequently built its own MCP server and plans to soon offer it as a product competing with Runlayer.

Runlayer's lawsuit claims that a Rippling employee reached out to Berman to warn him that his employer was building a "copy" of Runlayer's product. A Rippling spokesperson told TechCrunch that the employee has since revised that view (TechCrunch).

Rippling said it informed Runlayer of the patents it believed Runlayer had infringed soon after Runlayer filed its lawsuit. A Rippling spokesperson accused Runlayer of hypocrisy, saying Runlayer is infringing Rippling's inventions while accusing Rippling of violating intellectual property laws (TechCrunch).

Berman called Rippling's lawsuit a "desperate, retaliatory ploy" to distract from Rippling's alleged misappropriation of Runlayer's proprietary technology (TechCrunch).

Runlayer's July 28 complaint, filed in Manhattan federal court, seeks a jury trial, damages, attorney's fees, and a preliminary injunction blocking Rippling from developing or selling a competing product (New York Post).

The dispute lands at a juncture where MCP is still establishing its footprint as a connectivity standard for agentic AI. The protocol's open nature means that gateway implementations, security wrappers, and integration layers are where vendors are differentiating, and where the intellectual property terrain is being contested for the first time. Runlayer's product combines MCP gateway functionality with threat detection, positioning security as a value layer on top of the protocol rather than as a separate concern. Rippling's decision to build its own MCP server rather than license one suggests that, at least for large platform companies, the MCP gateway is becoming strategic infrastructure rather than a procurement line item.

The legal machinery here is not novel. Trade secret misappropriation claims followed by patent counterclaims is a well-established litigation pattern, particularly when a larger company has had access to a smaller company's technology under evaluation or partnership terms and then ships a competing product. What is unusual is that this is playing out over a protocol that is barely a year old in commercial deployment, and where the open standard itself is not in dispute but the surrounding implementation is. The outcome could set an early reference point for how IP claims are framed around products built on open agentic standards, especially when one party alleges that the other's implementation is derivative rather than independently developed.