The development of AI-based development tools, such as Claude Code and Cursor, combined with the emergence of the Model Context Protocol (MCP), is triggering a new wave of popularity for "mashups"—applications that combine data from many different sources into a single system.
What Happened
The emergence of specialized AI tools and standardized integration protocols allows experts in various subject areas to independently assemble complex internal systems. Creating custom software solutions that combine data from different services no longer requires deep programming knowledge: AI agents take on the role of developers, utilizing existing APIs.
Context
Traditionally, the value of SaaS platforms lay in their proprietary user interfaces (UI). However, the development of the Model Context Protocol (MCP) is creating an infrastructure where what matters critically is not how the interface looks, but how easily and effectively a service provides its data via API for interaction with AI agents.
Why It Matters for the Industry
For the industry, this signifies a fundamental shift: SaaS providers will face decreased traffic in their standard web interfaces as users move toward interacting with data through custom AI layers. The survival of companies will depend on their ability to maintain open APIs, protocols like MCP, and provide a flexible system of fine-grained permissions for agents.
Why It Matters for Users
The barrier to entry for developing useful software is significantly lowering. Ordinary users and business owners are gaining the ability to create their own "command centers"—unified workspaces combining CRM, email, spreadsheets, and other tools, without the need to hire a staff of developers.
What Is Not Yet Known / Limitations
There is a need for a thorough revision of approaches to access management and security when transitioning to automated integrations.
Sources
Author
Look at AI, Editorial Team