Slide deck
BackREST, SOAP, gRPC, GraphQL and MCP: pick by who calls
Pick an API style by who calls it: REST for outside developers, gRPC between your own services, GraphQL for front ends with many screens, SOAP only for old links. MCP is another kind: it wraps the other four as tools for AI agents, and is stateless since July 2026.
API guide · 27 October 2026
Five ways software talks to software
REST, SOAP, gRPC, GraphQL and MCP, explained for beginners and professionals.
REST · SOAP · gRPC · GraphQL · MCP1 / 15
The basics
What is an API?
An API is an agreed way for one program to ask another for something and get a predictable answer. Think of ordering in a restaurant.
You
The client: an app, a website or an AI agent that wants something.
The waiter
The API: the menu and the rules for ordering.
The kitchen
The server: the system that holds the data and does the work.
REST · SOAP · gRPC · GraphQL · MCP2 / 15
The basics
The five at a glance
Name What it is Think of it as REST Web addresses plus standard actions A library catalogue SOAP Formal XML messages with strict contracts A registered letter gRPC Fast binary calls between services A direct line between colleagues GraphQL One endpoint; you ask for exactly the fields you need A custom order form MCP A standard plug for AI agents to use tools and data A universal adapter REST · SOAP · gRPC · GraphQL · MCP3 / 15
The five · 1 of 5
REST: resources at web addresses
Best for: public web APIs, websites and mobile apps.
Step Example Request GET /orders/42Response 200 OK, with the order as JSON- Everything is a resource with its own address, such as an order, a user or a photo.
- Standard verbs: GET reads, POST creates, PUT or PATCH updates, DELETE removes.
- Cache-friendly: browsers and CDNs can store GET results.
REST · SOAP · gRPC · GraphQL · MCP4 / 15
The five · 2 of 5
SOAP: the formal envelope
Best for: connecting existing bank, insurance and government systems. Avoid it for new APIs.
Part Holds Envelope (XML) The whole message Header Security, routing and extras Body The actual request or reply - Strict contract: a WSDL file and XML schemas describe every message.
- Message-level security: WS-Security can sign and encrypt the message itself.
- Heavy: XML is verbose, so it is slow and awkward on mobile.
REST · SOAP · gRPC · GraphQL · MCP5 / 15
The five · 3 of 5
gRPC: fast calls between services
Best for: internal microservices, low latency and live streams.
In a .proto contract rpc GetOrder(OrderId) returns (Order);- Contract first: one .proto file generates client and server code in many languages.
- Compact and quick: binary messages over HTTP/2, with four streaming modes.
- Browser limits: web pages need gRPC-Web or a JSON gateway.
REST · SOAP · gRPC · GraphQL · MCP6 / 15
The five · 4 of 5
GraphQL: ask for exactly what you need
Best for: apps with many screens or clients sharing one data graph.
One query, one endpoint Ask for order(id: 42), and from it onlystatusand each item’sname- The client picks the fields, so there is no over-fetching and fewer round trips.
- Typed schema that tools can explore and check automatically.
- Extra care: caching needs extra work, and servers need depth and cost limits.
REST · SOAP · gRPC · GraphQL · MCP7 / 15
The five · 5 of 5
MCP: a standard plug for AI agents
Build one MCP server and any compatible AI app can use it, instead of one custom connector per product.
Tools
Actions the AI can run, such as creating a ticket.
Resources
Data the app can read, such as a file or a record.
Prompts
Ready-made templates a person can choose.
- Runs over stdio (local) or Streamable HTTP (remote), using JSON-RPC 2.0.
REST · SOAP · gRPC · GraphQL · MCP8 / 15
How they fit together
MCP sits on top of the others
MCP does not replace them. It wraps existing APIs as tools, so an AI agent can discover and call them in a standard way. Cloud gateways already turn REST, OpenAPI and GraphQL services into MCP tools.
Layer What it is Top An AI agent or chat app Middle An MCP server: tools · resources · prompts Bottom REST · GraphQL · gRPC · SOAP REST · SOAP · gRPC · GraphQL · MCP9 / 15
Comparing
Side by side
REST SOAP gRPC GraphQL MCP Message format JSON, mostly XML Protobuf (binary) JSON JSON-RPC 2.0 Transport HTTP Mostly HTTP HTTP/2 HTTP, usually POST stdio or Streamable HTTP Contract OpenAPI WSDL and XSD .proto file Schema (SDL) JSON Schema per tool Streaming Limited None Four modes Subscriptions Server events (SSE) HTTP caching Built in Almost none None Needs extra work Cacheable lists since 2026-07-28 Main caller Any developer Enterprise systems Other services Front-end apps AI agents REST · SOAP · gRPC · GraphQL · MCP10 / 15
Comparing
Speed depends on the workload
- 77%Lower latency for gRPC than REST on small payloads, 2.3 ms against 10.1 ms
- 15%Lower latency on large payloads
- The gap shrinks as messages grow. This is one 2026 benchmark, so test your own workload before choosing a protocol for speed.
- For MCP, the usual bottleneck is tokens in the AI’s context window, not the wire format.
REST · SOAP · gRPC · GraphQL · MCP11 / 15
Comparing
Security: what protects you, what to watch
MCP’s biggest risks sit in meaning, not transport: treat tool output as untrusted.
Option Main protection Check for REST TLS, OAuth 2.x, API keys Access checks on every object, rate limits SOAP WS-Security signing and encryption XML parser hardening gRPC TLS or mutual TLS, per-call tokens A deadline on every call GraphQL Depth and cost limits, timeouts Costly queries and batching abuse MCP OAuth 2.1, least privilege, approvals Prompt injection, token passthrough REST · SOAP · gRPC · GraphQL · MCP12 / 15
Deciding
Which one should I use?
Situation First choice Why Public API for outside developers REST + OpenAPI Easiest to adopt and cache Internal service-to-service calls gRPC Fast and strongly typed An app with many different screens GraphQL Fetch only needed fields Legacy bank or government link SOAP Wrap it behind REST Let an AI agent use your tools MCP One plug for many AI apps REST · SOAP · gRPC · GraphQL · MCP13 / 15
Deciding
One company, several styles
Style Serves REST Partners and third-party developers GraphQL Your own web and mobile front ends gRPC Microservices talking to each other SOAP Legacy systems, isolated behind an integration layer MCP AI agents, through a gateway that handles identity, policy and audit REST · SOAP · gRPC · GraphQL · MCP14 / 15
Takeaways
Three things to remember
- Pick by who calls you: outside developers, your own services, your own front ends or an AI agent.
- MCP sits on top of the other four. It does not replace them.
- Test with your own workload, and secure every layer.
REST · SOAP · gRPC · GraphQL · MCP15 / 15