MCP Startup Runlayer Sues Rippling Over Gateway Product

Runlayer, a startup building infrastructure around the Model Context Protocol (MCP), is suing HR and IT platform Rippling. The allegation: Rippling evaluated Runlayer's MCP gateway product, then walked away and built a competing version itself.

What happened

According to the report, Rippling evaluated Runlayer's MCP gateway — a product designed to sit in front of MCP connections and manage how AI agents access tools and data — before deciding to build its own version rather than continue with Runlayer. Runlayer is now pursuing legal action over what it characterizes as the theft of its product idea. [VERIFY]: the specific legal claims (trade secret misappropriation, breach of contract, or another theory), the court where the suit was filed, and any monetary damages sought.

Why it matters

For builders: MCP, the open protocol that lets AI agents connect to external tools and data sources, has become one of the most contested pieces of infrastructure in the agentic AI stack. A "gateway" layer — controlling authentication, access, and observability for MCP connections — is a natural chokepoint that both startups and platform incumbents want to own. This dispute is a preview of the land-grab likely to play out across the MCP ecosystem as more platforms decide whether to buy, partner, or build.

For enterprise software buyers: Rippling is a large, well-resourced HR and IT platform with the ability to build infrastructure in-house after seeing how a smaller vendor solved the problem. That dynamic — evaluate a startup's product, then build a competitor — is a familiar risk in enterprise sales, and it's one MCP-focused startups in particular will need to navigate as bigger platforms race to add agentic capabilities.

For the broader MCP ecosystem: the case underscores how quickly MCP tooling has moved from a niche protocol to something platforms are actively fighting over commercially, barely a couple of years after Anthropic introduced it.

What's unknown

The publicly available details are thin. It isn't clear from reporting what specific technical or product elements Runlayer alleges were copied, how long the evaluation relationship lasted, whether any contracts or NDAs governed the engagement, or what Rippling's response to the allegations has been. [VERIFY]: Rippling's official statement, if any, and the current status of its in-house MCP gateway product.

What to watch

• Rippling's public response to the lawsuit
• Whether other MCP infrastructure startups report similar "evaluate then build" experiences with larger platforms
• How courts approach product-idea disputes in a fast-moving, open-protocol ecosystem where much of the underlying technology (MCP itself) is not proprietary to either party
• Whether this accelerates consolidation or partnership deals between MCP startups and the platforms they sell into

Source: TechCrunch