AI agents will only use MCP, so do we still care about traditional APIs?

In the rapidly evolving landscape of AI, the Model Communication Protocol (MCP) has emerged as a significant standard for agent-to-tool integration, with 78% of enterprise AI teams implementing MCP-backed agents within just eighteen months. Despite this swift adoption, traditional APIs remain crucial, as they continue to serve as the foundation for MCP servers, retaining essential business logic, data contracts, and security models. While MCP changes the consumer dynamics, it does not alter the underlying APIs, which remain vital for partners, mobile apps, and internal services. The governance challenges associated with MCP mirror those of traditional API management, requiring similar oversight and policy enforcement. Although some predict a strategic shift towards MCP, the argument that traditional APIs will become obsolete is refuted by the reality that infrastructure tends to build upon itself rather than replace existing layers. The evolution of MCP signifies not the end of traditional APIs, but rather their adaptation to meet the demands of AI agents as their most challenging consumers yet.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.