Apollo MCP Server started with a simple ask. When MCP first came out, customers wanted their agents to reach their own GraphQL APIs, so we built a server that turns GraphQL operations into MCP tools, with no hand-written tool per endpoint.
The requests that came next were not about their own graphs at all. They wanted their agents to reach GraphOS. Answering "is my graph healthy?" meant a tour across half a dozen Studio pages: launch history, composition errors, lint reports, router status, operation latency, and error rates. The answer was always in there. Assembling it was the work.
So we became our own customer. GraphOS MCP Server is Apollo MCP Server, configured against Apollo's own GraphQL API and hosted at mcp.apollographql.com, so you run nothing.
In this session, we cover:
What you can actually ask, demonstrated live. We start with "Have the recent launches on my graph been stable?" and work up to the prompt this session is named after: "Is my graph healthy?"
The two ways to connect. API keys work best for coding agents in the terminal. OAuth is better for non-developers who use Claude Desktop or ChatGPT.
What your agent is allowed to see. The documentation tools are read-only so public. An API key scopes the agent to a single graph. An OAuth login signs in as you, so it reaches every graph you can reach.
Because GraphOS MCP Server is Apollo MCP Server with a configuration file, everything in the demo is a pattern you can apply to your own graph.
Meet your speakers
