Now Rippling is counter suing tiny startup Runlayer

The immediate change is the escalation from a single complaint to two opposing lawsuits, with Rippling now asserting patent rights against Runlayer. For engineers, this means any code that incorporates Runlayer’s MCP gateway could be subject to infringement claims if it overlaps with Rippling’s patented implementations. The legal cost of defending or settling such claims adds a non-technical overhead to product planning.

Rippling’s decision to build its own MCP server after the trial indicates a strategic shift toward internalizing technology that was once sourced from a startup. Teams that were relying on Runlayer’s gateway must now evaluate whether to continue using it, switch to Rippling’s offering, or develop an alternative that steers clear of the disputed patents. This adds design and integration effort, as well as potential delays while the legal outcome is pending.

The lawsuit also underscores a broader market warning: enterprises can quickly move from customer to competitor, and startups may find their IP exposed when large customers test their products without a binding agreement. Engineers should therefore negotiate clear IP clauses and consider the risk of a partner turning a trial into a competing product. Without such safeguards, the relationship can deteriorate, leading to costly litigation.

From a technical standpoint, the MCP standard itself is open, but the specific implementations claimed as patented by Rippling may limit how engineers can use or extend the protocol. If a component of the MCP gateway is deemed infringing, any downstream services that depend on that component could be forced to re-architect. This risk is most acute for teams building AI agents that rely on tight integration with data and software systems via MCP.

Finally, the public framing of the case as a buyer-seller cautionary tale suggests that future collaborations may involve stricter contractual terms, such as defined pricing, IP ownership, and exit clauses. Development teams should anticipate more rigorous legal review before adopting nascent AI-infrastructure startups, potentially slowing the rapid prototyping cycles that have become common in the AI-powered era.