Apollo MCP Server
Apollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
- 317 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can run mutations against a production API
- Handles GraphOS keys
Install
- Works in
Manual install
curl -sSL https://mcp.apollo.dev/download/nix/latest | shBinary install for Linux and macOS per Apollo docs.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can run mutations against a production API
- Handles GraphOS keys
This is third-party code. Review the repository files before installing.
What it does
The server sits in front of your GraphQL graph and publishes chosen operations as MCP tools. You define which queries and mutations the agent may use and configure the server with a config file. The agent gets controlled API access instead of arbitrary schema queries. It is written in Rust, ships as a binary and a Docker image, and can run alongside a local graph via Rover CLI.
Who it is for. For teams with a GraphQL API on Apollo who want to expose it to agents and AI apps.
Good fit when
- You want an agent to reach company data through an existing GraphQL API
- You need to restrict the agent to predefined operations
- You want to see how an agent uses the graph during local development
Not a fit when
- Your API is not GraphQL
- You want a server that works without setup: you must define the graph, operations and config first
Example request
Use the Apollo tools to find the latest orders for the customer ivan@example.comMCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
APOLLO_KEYsecret- GraphOS key for graphs in Apollo's cloud
APOLLO_GRAPH_REF- Graph reference in GraphOS
Limitations
It needs a graph, operation definitions and a config file; install and setup are in the Apollo docs. GraphOS integration requires an Apollo account plus APOLLO_KEY and APOLLO_GRAPH_REF. With your own graph and local operations no external services are needed.
How to disable. Stop the server process or container and remove its address from your MCP client config.
FAQ
What do I need before starting?
A graph for the server to front, GraphQL operation definitions to publish as tools, a config file and an MCP client to connect.
Can it run alongside a local graph?
Yes, Rover CLI 0.37 or newer starts it with the graph via rover dev with the --mcp flag.
Discussion
No questions or reviews yet.
Related
MCP serversmcp-graphql: MCP server for GraphQL APIs
mcp-graphql
Two GraphQL tools for MCP clients: the agent fetches your API schema and runs queries against a single endpoint
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
Firebase MCP Server
Firebase CLI and MCP Server
Official Firebase MCP server from the Firebase CLI: projects, Firestore, Auth, Crashlytics, Remote Config and function logs
A Laravel and Lumen package that adds an MCP endpoint to your app's routes and attaches your own tools to it
Two official Prisma MCP servers: a local one for migrations and Prisma Studio, and a remote one for managing Prisma Postgres databases
Instant REST and MCP over PostgreSQL: the agent reads an existing database through an MCP endpoint with no backend to write
README in short
The README briefly explains the server's purpose and lists four prerequisites: a graph, operations, a config and an MCP client. It mentions building from source with cargo build and points to Apollo docs for other install options, a quickstart and the config reference. MIT licensed.