Runlayer, a Model Context Protocol (MCP) startup, filed a lawsuit against Rippling, a workforce management software company, alleging that Rippling stole its MCP gateway product concept. The dispute centers on Rippling's evaluation of Runlayer's technology before deciding to develop a competing solution internally.
The MCP gateway market represents a growing segment in AI infrastructure, enabling seamless integration between large language models and enterprise tools. Runlayer built its platform specifically to simplify these connections, positioning itself as a bridge between AI systems and business applications. Rippling, which serves over 10,000 companies with HR, IT, and finance solutions, evaluated the Runlayer product as a potential partner or acquisition target.
According to Runlayer's allegations, Rippling examined the startup's gateway architecture and functionality during this evaluation period. Rather than proceeding with a partnership or acquisition, Rippling chose to build its own MCP gateway product, leveraging insights gained during its technical review.
This lawsuit reflects a recurring tension in the startup ecosystem. When larger established companies evaluate emerging technologies, smaller startups risk exposing proprietary designs and methodologies. The legal question hinges on whether Rippling used specific trade secrets or merely applied general knowledge gained during the evaluation process. Patent law and trade secret protections define these boundaries, but enforcement remains costly and uncertain.
Rippling has not publicly responded to the lawsuit. The company's decision to build internally rather than partner or acquire suggests either confidence in its engineering capabilities or concerns about Runlayer's product maturity.
The MCP gateway space remains nascent, with multiple vendors competing to establish standards and market share. This dispute could shape how enterprise software companies approach vendor evaluations going forward, potentially making startups more cautious about sharing technical details with larger potential partners.
The outcome carries implications beyond Runlayer and Rip