APIs · Model Context Protocol · AI Agents · Software Engineering · Web Infrastructure · Comparison BriefThe five as they stand on 27 October 2026
Five ways software talks to software
REST, SOAP, gRPC, GraphQL and MCP: pick by who calls
REST, SOAP, gRPC and GraphQL answer one question: how does one program call another? MCP, the Model Context Protocol, answers a different one: how does an AI model find a capability and use it safely? The first four are rivals only in part, since each suits a different caller. MCP usually sits on top of them rather than replacing them. Its newest specification, dated 28 July 2026, made the protocol stateless.
What Happened
Where each of the five stands Latest specification and steward, October 2026
- 2026-07-28MCP’s current revision: stateless, governed by the Agentic AI Foundation under the Linux Foundation
- 3.2.0OpenAPI, the usual contract for REST, dated 19 September 2025
- 2025GraphQL’s September edition, the first since October 2021
- 2017gRPC joined CNCF as Incubating, and it is still listed there
- 2007SOAP 1.2 Second Edition, a W3C Recommendation and still the current version
Confirmed
The MCP 2026-07-28 changes come from its maintainers’ post and changelog. The handshake and session header are gone, each request describes itself, method and tool names travel in headers, list results carry cache hints, and Roots, Sampling and Logging are deprecated with at least twelve months’ notice. Each version and date above comes from its own steward.
Confirmed, but the sources disagree
How widely MCP is used. On the same day, the MCP blog said the Tier 1 SDKs see “close to half-a-billion downloads a month”, while Anthropic said MCP had “surpassed 400M monthly SDK downloads”. Both are promotional figures and neither was checked independently.
Proposed, not standard
MCP over gRPC. In January 2026 Google Cloud proposed gRPC as a pluggable MCP transport and said the core maintainers had agreed to support pluggable transports in the SDKs. Spotify says it runs it experimentally in-house. The official transports are still stdio and Streamable HTTP.
Timeline
From XML envelopes to a plug for AI agents Dates as each steward or source gives them
- Jun 1998XML-RPC appears; SOAP grows out of it (Wikipedia).
- 2000Roy Fielding names and defines REST in his doctoral dissertation (Wikipedia).
- 27 Apr 2007SOAP 1.2 Second Edition becomes a W3C Recommendation (W3C).
- Mar 2015Google decides to build the successor to Stubby, its internal RPC system since about 2001, as open source; the result is gRPC (Wikipedia).
- 14 Sep 2015Facebook releases GraphQL publicly, after developing it since 2012 (Wikipedia).
- 16 Feb 2017CNCF accepts gRPC at the Incubating level (CNCF).
- Jun 2022RFC 9110 restates HTTP’s semantics, the ground REST stands on (RFC Editor).
- Nov 2024Anthropic introduces MCP (Wikipedia).
- 15 Aug 2025AWS introduces AgentCore Gateway, which turns OpenAPI and Smithy APIs and Lambda functions into MCP tools (AWS).
- 8 Sep 2025GraphQL’s September 2025 edition is announced, the first since October 2021 (GraphQL).
- 19 Sep 2025OpenAPI 3.2.0 is published (OpenAPI Initiative).
- 4 Nov 2025Anthropic shows one MCP workflow falling from 150,000 to 2,000 tokens when the agent writes code instead of loading every tool definition (Anthropic).
- 9 Dec 2025Anthropic donates MCP to the Agentic AI Foundation, co-founded with Block and OpenAI under the Linux Foundation; the maintainers stay the same (Anthropic; MCP blog).
- 14 Jan 2026Google Cloud proposes gRPC as a pluggable transport for MCP (Google Cloud).
- 29 Apr 2026A Tech Insider benchmark puts gRPC at 2.3 ms against REST’s 10.1 ms on small payloads, with a much smaller gap on large ones (Tech Insider).
- 28 Jul 2026MCP 2026-07-28 ships, with a stateless core, header routing, cacheable lists and a deprecation policy; Anthropic calls it the fifth spec release (MCP blog; Anthropic).
The Argument
Choose by caller, then put MCP on top What the specifications and their stewards support, and what complicates it
Each style suits one caller. REST rides on HTTP’s own semantics, so a GET can be cached by browsers, proxies and CDNs, and RFC 9110 calls the conditional GET “the most efficient mechanism for HTTP cache updates”. That suits outside developers. gRPC needs HTTP/2 and binary Protocol Buffers, and Microsoft’s architecture guide says it “should be the primary choice for direct synchronous communication between microservices”. A browser, though, needs gRPC-Web or a JSON gateway, and gRPC-Web cannot do client or bidirectional streaming. GraphQL lets the client name the fields it wants from one endpoint, which suits front ends with many screens. SOAP’s WSDL contracts and message-level signing keep it alive in older enterprise links. MCP is a different kind of layer: a model, not a compiler, reads its contract, and the specification warns that “Tools represent arbitrary code execution”. Gateways from Microsoft, AWS and Apollo already turn REST, OpenAPI and GraphQL into MCP tools without rebuilding the API underneath.
- 0Sessions an MCP 2026-07-28 server must keep: any request can land on any instance
- 98.7%Token saving in one Anthropic MCP example, from 150,000 to 2,000
- 77%gRPC’s lower latency than REST on small payloads, in one benchmark
What complicates it
Speed figures do not travel. The same Tech Insider benchmark that gives gRPC 77% lower latency on small payloads gives it only 15% on large ones. The 98.7% token saving is Anthropic’s own best case, and running code that way needs a secure sandbox. MCP also deprecates things quickly: Roots, Sampling and Logging were deprecated less than two years after the first release, though they keep working for at least twelve months.
What Others Add
Securing each one, and wrapping them for agents Each item as the named source gives it
| Style | What to watch | Source |
|---|---|---|
| GraphQL | Query depth and amount “can both be unlimited which may lead to a DoS”. Set limits, cost analysis and timeouts, and watch for batching, where one request carries many operations. | OWASP |
| MCP | Token passthrough, where a server forwards a client’s token downstream without checking that it was issued to that server, is named an anti-pattern. Tool descriptions count as untrusted unless the server is trusted, and hosts need explicit user consent before calling a tool. | MCP specification |
| gRPC | Set a deadline on every call. In a browser, gRPC-Web cannot call client-streaming or bidirectional methods. | gRPC; Microsoft |
| Protobuf | Moving from proto2 or proto3 to editions such as 2024 changes the generated code, not the wire format. | Protocol Buffers |
Gateways
REST and OpenAPI into MCP
- Azure API Management can expose a managed REST API as a remote MCP server. It offers tools only, not resources or prompts.
- AWS’s AgentCore Gateway converts OpenAPI and Smithy APIs and Lambda functions into MCP tools.
Graph and RPC
GraphQL and gRPC into MCP
- Apollo MCP Server exposes GraphQL operations as tools, and its
mutation_modedefaults tonone, so nothing can write until someone allows it. - For gRPC, Google Cloud’s transport is a proposal, so a translating gateway is still the usual route.
- Apollo MCP Server exposes GraphQL operations as tools, and its
Conclusion
Which one suits which caller Each card: who it is for, its strongest point, and the trade-off
REST
Outside developers and the web
- Best at: the lowest barrier, the most tools, and caching by browsers and CDNs.
- Trade-off: over-fetching and extra round trips.
gRPC
Your own services, talking to each other
- Best at: typed contracts, small binary messages, deadlines and four streaming modes.
- Trade-off: no HTTP caching, and browsers need gRPC-Web or a JSON gateway.
GraphQL
Front ends with many screens
- Best at: letting the client ask for exactly the fields it needs.
- Trade-off: caching needs extra work, and servers need depth and cost limits.
SOAP
Existing bank, insurance and government links
- Best at: security on the message itself, which survives every hop between systems.
- Trade-off: verbose and heavy; wrap it behind REST rather than spread it.
MCP
AI agents using your tools and data
- Best at: one integration that any compatible AI app can find and call.
- Trade-off: the risks lie in meaning, such as prompt injection and token passthrough, and the spec still moves fast.
- Ask who calls before asking what is fastest. A single benchmark is not your workload.
- Build new MCP servers for 2026-07-28. Keep no session, let gateways route on the headers, and leave Roots, Sampling, Logging and HTTP+SSE alone.
- Treat every MCP tool as code that runs. Start writes switched off, ask a person before sensitive actions, and never pass a client’s token through.
Quick notes
- David Soria Parra and Den Delimarsky, “The 2026-07-28 Specification”, MCP blog, 28 Jul 2026
- Model Context Protocol, 2026-07-28 changelog, specification, versioning, security best practices and Streamable HTTP pages
- David Soria Parra, “MCP joins the Agentic AI Foundation”, 9 Dec 2025
- Anthropic, “Donating MCP to the Agentic AI Foundation”, 9 Dec 2025
- Adam Jones and Conor Kelly, “Code execution with MCP for efficient agents”, Anthropic, 4 Nov 2025
- Anthropic, “Bringing MCP 2026-07-28 to Claude”, 28 Jul 2026
- Chris Wood, “Announcing OpenAPI v3.2”, 23 Sep 2025
- OpenAPI Specification v3.2.0, 19 Sep 2025
- CNCF, gRPC project page
- Lee Byron, “Announcing the September 2025 Edition of the GraphQL Specification”, 8 Sep 2025
- W3C, SOAP Version 1.2 Part 1 (Second Edition), 27 Apr 2007
- Fielding, Nottingham and Reschke, RFC 9110, Jun 2022
- Wikipedia, “REST”, “GraphQL”, “SOAP”, “gRPC” and “Model Context Protocol”
- Nadia Dubois, “gRPC vs REST 2026”, Tech Insider, 29 Apr 2026
- Microsoft Learn, gRPC in the .NET cloud-native guide, gRPC-Web in ASP.NET Core, Compare gRPC services with HTTP APIs, and Expose REST API as MCP server
- Protocol Buffers, Editions Overview
- gRPC, Core concepts
- OWASP, GraphQL Cheat Sheet
- Patel, Rustagi and Liu, “Introducing Amazon Bedrock AgentCore Gateway”, AWS, 15 Aug 2025
- Apollo GraphQL, Apollo MCP Server config file reference
- Victor Moreno and Mark D. Roth, “A gRPC transport for the Model Context Protocol”, Google Cloud, 14 Jan 2026. All read 27 Oct 2026.
Reliable
Worth believing
Sharing a subject
- The Claude Code Quality Postmortem — Three Unrelated ChangesAI Agents · Software Engineering
- 9 Billion Requests a Day, Moved Without Rebuilding a FileSoftware Engineering · Web Infrastructure
- The Harness Ships, the Governance Doesn’tAI Agents · Software Engineering
- Local LLMs and Buying a Mac — A Technical ReportAI Agents
- Grok Build Shipped Whole Repos to xAI's CloudAI Agents
- Five Names for One Stack, and No Agreed OrderAI Agents
- AI Reasoning Traces: Encrypted, Not HiddenAI Agents
- Enough, or Less? Context Engineering Said Both in One WeekAI Agents
- It Began as Tuning an Agent. By March It Meant Everything but the Model.AI Agents
- One Term, Coined Twice, Two Weeks Apart. The Joke Won.AI Agents
- Everyone Agrees You Should Write Loops. Nobody Agrees What One Is.AI Agents
- Agents That Hacked Real Systems to Pass Their Own TestsAI Agents
- 533 Bytes an Entry, 100 Terabytes a FleetSoftware Engineering
- OpenAI Cuts Off Cursor: What Stops, and What Doesn'tSoftware Engineering
- Shunting Bulk Reads to a Cheaper Model — What the 90% Actually CutsAI Agents
- Who Gets Told When an Agent Breaks SomethingAI Agents
- Sophistication Stopped Telling You WhoAI Agents
- The Boundary Is Not the ModelAI Agents
- Apache, Nginx and Caddy: which HTTPS web serverWeb Infrastructure
Sharing a source domain
- Enough, or Less? Context Engineering Said Both in One Weekanthropic.com · claude.com · github.com · wikipedia.org
- The Tricks Moved Into the Model. The Writing Stayed.anthropic.com · claude.com · microsoft.com · wikipedia.org
- Five Names for One Stack, and No Agreed Orderanthropic.com · claude.com · github.com
- It Began as Tuning an Agent. By March It Meant Everything but the Model.anthropic.com · github.com · wikipedia.org
- Sophistication Stopped Telling You Whoanthropic.com · google.com · microsoft.com
- The Claude Code Quality Postmortem — Three Unrelated Changesanthropic.com · github.com
- Grok Build Shipped Whole Repos to xAI's Cloudgithub.com · wikipedia.org
- One Term, Coined Twice, Two Weeks Apart. The Joke Won.claude.com · github.com
- Everyone Agrees You Should Write Loops. Nobody Agrees What One Is.claude.com · microsoft.com
- The Harness Ships, the Governance Doesn’tanthropic.com · microsoft.com
- Shunting Bulk Reads to a Cheaper Model — What the 90% Actually Cutsclaude.com · github.com
- The Boundary Is Not the Modelanthropic.com · claude.com
- A race in Linux's TCP handshake, open since kernel 4.4amazon.com · anthropic.com
- Apache, Nginx and Caddy: which HTTPS web servertech-insider.org · wikipedia.org
- The Fubon Arts Court Skybridge — What It Means for Zhongxiao Fuxing Stationwikipedia.org
- The AISI Cyber Evaluation of Claude Mythos Previewanthropic.com
- Local LLMs and Buying a Mac — A Technical Reportgithub.com
- 9 Billion Requests a Day, Moved Without Rebuilding a Filegithub.com
- Google's Opus HD Joins Hi-Res AUDIO WIRELESSrfc-editor.org
- Avalanche's RWA Boom, and Why AVAX Need Not Followgithub.com
- China, North Korea and the Tumen River Sea Outletwikipedia.org
- The Spark That Starts a Fire — Anonymous Tip-Offs and Singapore's CPIBwikipedia.org
- Cryptographic Weakness Discovery — Reading Anthropic Against Its Own Papersanthropic.com
- Swap Across Five Platforms — Compress First, Spill Latermicrosoft.com
- AI Reasoning Traces: Encrypted, Not Hiddenclaude.com
- Agents That Hacked Real Systems to Pass Their Own Testsanthropic.com
- Dorado v4 to v6 — What Changed, How Much, and Whether It Was Goodgithub.com
- Signed in Pencilwikipedia.org
- The Polyamory Words, and the One Nobody Can Datewikipedia.org
- AWS Adds 2 Million More Nvidia GPUsamazon.com
- 533 Bytes an Entry, 100 Terabytes a Fleetrfc-editor.org
- Nineteen Numbers, Three Forces of Fourwikipedia.org
- Three Cuts Into the Uncuttablewikipedia.org
- Who Gets Told When an Agent Breaks Somethinganthropic.com
- Eighteen Hells, Ten Dates, and the Seams Between Themwikipedia.org
- Two Routes to Godhood, and What Each Leaves in the Archivewikipedia.org
- Abrahamic Religions, and the Historians Who Dispute the Labelwikipedia.org
- Not a Ladder, a Palimpsestwikipedia.org
- Forty-Three Years Was Last Month’s Pricegithub.com
- The Dying, Not the Bereavedwikipedia.org
- Anchored, Not Canonwikipedia.org
- The Colour Is the Vitaminwikipedia.org
- Three Legal Systems: Malaysia, Singapore and Taiwanwikipedia.org
- Dairy in East and Southeast Asiawikipedia.org
- Seven sequence aligners, three jobsgithub.com
- Six single-cell analysis platforms, comparedgithub.com
- Binance’s BNB: many chains, one coinwikipedia.org
- Brazil and Serbia: two upsets on one Sundaywikipedia.org
- Rewrite, preserve or police: three agencies that run timewikipedia.org
- Active investing: who decides, and where the reason comes fromwikipedia.org
- Passive investing: the whole market, by its valuewikipedia.org