Is MCP still relevant now that AI agents can just crawl the website/Swagger docs directly?
Summary
A discussion on whether the Model Context Protocol (MCP) remains relevant as AI agents increasingly crawl websites or Swagger/OpenAPI docs directly, comparing the reliability and advantages of each approach.
Similar Articles
Why use MCP when Agents can use APIs directly?
The article questions the redundancy of MCP in agentic workflows when AI agents can directly call APIs, noting MCP's value in consensus and governance but suggesting it might be unnecessary for web API-based implementations.
Which MCP servers give AI agents real business capabilities in 2026??
A practitioner shares their experience with MCP (Model Context Protocol) servers for business work, detailing which ones provide real read/write capabilities (e.g., Postgres MCP, HubSpot MCP, PostFast) and which disappoint (e.g., Slack MCP, Google Ads MCP), while highlighting major security concerns like low OAuth adoption and high vulnerability rates.
@swyx: explain this
This article explains the Model Context Protocol (MCP) for building pluggable AI agent architectures, detailing lessons from building an MCP server at Sentry, including OAuth 2.1 integration, designing agent-friendly tool interfaces, and current ecosystem limitations.
Is MCP actually reducing integration work for agents?
The article explores whether the Model Context Protocol (MCP) effectively reduces integration work for AI agents by standardizing agent-tool communication, comparing native MCP integration in Evose to manual wiring in other stacks like LangGraph and CrewAI.
The 'agent web' is coming — where AI agents talk directly to each other instead of scraping websites
The article discusses the future of AI agents communicating directly with each other via APIs and protocols like MCP, bypassing human-oriented web interfaces, and the author asks the community about adoption timelines and use cases.