Anthropic released Model Context Protocol (MCP) seems to have become the winning protocol choice for the AI industry. Despite the number of companies announcing MCP servers, MCP is technically not a standard. But many see MCP as one of the main protocols, if not the potential winner, for the agentic ecosystem. A lot of MCP’s attractiveness comes from streamlining how models interact with data and tools. Before MCP, developers pointed models and agents to data with APIs. However, APIs are imperfect connectors, especially for agents that access data to complete tasks automatically. Unlike APIs, organizations can configure their MCP servers with custom instructions laying out what agents can or cannot access. The server can “ask” an agent for its identity and determine if it can tap information on the MCP client side. Companies have more of a say on what outside agents can access on their end, giving MCP more directionality from the enterprise. Sagar Batchu, co-founder and CEO of API tooling company Speakeasy, said MCP transforms the work interface and API to a chat interface. He said MCP makes it so Speakeasy and its customers don’t need to rewrite or manually maintain APIs constantly. Yaniv Even Haim, chief technology officer of website builder Wix, told that MCP aligns with the company’s goals because it believes MCP can act as a “bridge” for its AI development workflows. “Wix chose the MCP model in particular because it aligns with the industry’s shift toward LLM-powered development, where context-rich, intelligent interfaces are key,” Haim said. For many companies, MCP will be one of many protocols they support as their customers decide which interoperability and agent communication methods to use. The growing adoption of MCP, for the varied reasons many companies have, proves that demand for standards is only growing.