MCP: Is GraphQL the Right “Tool” For the Job?
summary
Argues that GraphQL plus federation is a better MCP backbone than dumping REST: GraphQL’s selection sets cut token waste, a strongly typed schema gives live machine-readable contracts, and persisted queries become curated MCP tools exposed by Wundergraph’s gateway. Demonstrates a federated “API days” graph (sessions, speakers, locations, ratings) wired into Cosmo, shows MCP inspector calling persisted queries and a rating mutation that updates counts, and warns performance drops past ~30 tools and that models reliably chain only ~1–2 calls. federated graph persisted operations
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:51What is MCP and LLMs
- 3:36REST APIs vs MCP/AI
- 7:26GraphQL for MCP/AI
- 9:13Federation benefits
- 11:19Developing with GraphQL & LLMs
- 12:23Securing GraphQL for MCP
- 13:48Live GraphQL demo
- 19:51Agents in GraphQL stages
- 20:34Q&A
related talks
21mSimplifying MCP Tool Sprawl With GraphQL
26mAsk, Don't Fetch: Why GraphQL + MCP Is the Native Language of AI Agents
29mBuilding MCP Apps With GraphQL Patterns You Already Know
47mSchema Design in the Age of AI: Pragmatic Patterns to Evolve and Ship Fast
27mPanel: APIs for AIs
36mGraphQL Federation - The @key to Your Platform API Strategy
37mThe Future of GraphQL in the Enterprise Panel Discussion by GraphCMS
30mWhy GraphQL vs. Why not GraphQL