Runlayer Sues Rippling: Startup Accuses HR Giant of Copying Its MCP Gateway

Startup Runlayer sued Rippling on July 28, 2026, accusing it of stealing a product idea. According to TechCrunch, Rippling first examined Runlayer's MCP gateway in the role of a prospective customer, then released its own similar product.

What is an MCP gateway

An MCP gateway is a security layer between AI agents and external tools. Every connection made over the MCP protocol passes through it, and it handles authentication, access control, permission limits and logging of each request.

Anthropic introduced the MCP (Model Context Protocol) protocol itself in November 2024 as an open standard that lets language models access external data, services and tools directly. When a business connects AI agents to email, a CRM and internal databases, a security question arises: what exactly is the agent allowed to read and do? The gateway answers that question. The market for such products is only beginning to take shape, and Runlayer is one of its early players. Control at this level reduces the risk of data leaks and of an agent performing unwanted actions on a forged command, which is why large companies are adopting gateways more and more actively.

What Rippling is accused of

Runlayer claims that Rippling, under the guise of evaluating a possible deal, gained access to its MCP gateway, figured out how the product works, and then built a competing equivalent in-house instead of buying or licensing it. The startup regards this as appropriation of its product idea and is seeking protection in court.

The "evaluate first, copy later" scenario is a long-standing sore point in relations between startups and large corporations. During demos and pilots, a small company reveals its know-how to a potential buyer that has enough resources to rebuild the product itself.

• Plaintiff: Runlayer, a startup developing an MCP gateway for AI agents
• Defendant: Rippling, a US workforce and IT management platform
• Core of the suit: Rippling evaluated Runlayer's product, then released its own equivalent
• Date the suit was filed: July 28, 2026 (according to TechCrunch)
• Technology at issue: MCP (Model Context Protocol), an Anthropic standard since November 2024

Rippling gained access to Runlayer's product posing as a prospective customer, then built a competing MCP gateway in-house.

Those are the startup's claims, as reported by TechCrunch.

Why the case matters for the market

In the year and a half since its launch, MCP has grown from a niche protocol into the de facto standard for connecting AI agents to data, and the infrastructure layer around it has become a subject of fierce competition. The Runlayer–Rippling dispute shows that the AI market is no longer fought over models alone, but also over the "pipes" through which agents work safely with corporate systems. Other startups and large cloud providers are going after this same layer.

This is not Rippling's first high-profile corporate conflict. In March 2025, the company itself was the plaintiff, accusing its competitor Deel of corporate espionage. Now the roles are reversed: the accuser is a small startup, and Rippling is the defendant, suspected of copying someone else's work. One thing links both cases: conflicts over other companies' ideas and data are becoming a routine part of the enterprise software race.

What this means

Runlayer v. Rippling is a warning to anyone building infrastructure for AI agents: demoing a product to a large prospective customer carries the risk that the customer will release its own version instead of paying. The court has not yet issued a ruling, but the dispute itself has already drawn attention to how vulnerable startups are when they sell their products to future competitors. As the MCP market grows, there will be more disputes over ideas and over the limits of "evaluation before purchase," and the outcome of Runlayer's case could set a benchmark for the whole industry.