# Apollo MCP Server

Turns GraphQL operations into tools an AI agent can call by name. Useful when a model needs to reach your GraphQL API for real, not just read a description of it.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 317
- Author: apollographql
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/apollographql/apollo-mcp-server
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/apollo-mcp-server

## What it does

The server sits between an MCP client and your GraphQL graph. Each operation you list becomes a tool the agent can see and invoke, so calls go through your existing API instead of guesswork.

Four pieces have to line up: a graph, definitions for the operations to expose, a config file for the server, and a connected MCP client. Leave out the operation definitions and the tool list stays empty. The quick way to start is the container image: `docker run -i --rm ghcr.io/apollographql/apollo-mcp-server:v2.0.0`.

Rust on your machine opens a second route. `cargo install --locked apollo-mcp-server` pulls the crate with the dependency versions pinned at release time; `cargo build` from the repo root puts a binary in `target/debug` instead.

## Requirements
- Needs: Docker

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add apollo-mcp-server -- docker run -i --rm ghcr.io/apollographql/apollo-mcp-server:v2.0.0
```

### Codex

**Platform CLI**
```bash
codex mcp add apollo-mcp-server -- docker run -i --rm ghcr.io/apollographql/apollo-mcp-server:v2.0.0
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "apollo-mcp-server": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/apollographql/apollo-mcp-server:v2.0.0"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "apollo-mcp-server": {
            "type": "stdio",
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/apollographql/apollo-mcp-server:v2.0.0"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add apollo-mcp-server docker run -i --rm ghcr.io/apollographql/apollo-mcp-server:v2.0.0
```

## When to use it
- Let an agent call GraphQL operations directly
- Turn a file of queries into MCP tools
- Wire a GraphQL API into an MCP-compatible client
- Build the server from source when containers are out

## Example prompts
- Connect Apollo MCP Server to my graph and list the tools it exposes
- Add the operation in `operations/getUser.graphql` to the server config
- Check whether my MCP client can see the tools from the graph

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md