apollo-mcp-server

We need to translate the given text from English to French. The text describes an agent skill that connects AI agents to GraphQL APIs via MCP. It mentions specific terms: "Model Context Protocol", "GraphQL", "MCP", "GraphOS Studio", etc. These should be preserved as is. Also "apollo-mcp-server" is the name to preserve but it's not in the text, so we ignore. The text includes technical terms like "introspection", "operation tools", "minification mode", "token usage", "authentication", "static headers". We need to translate the rest naturally. The text: "Connect AI agents to GraphQL APIs through the Model Context Protocol with built-in introspection and operation tools. Exposes GraphQL operations as MCP tools; supports three operation sources: local files, GraphOS Studio collections, and persisted query manifests Provides four introspection tools (introspect, search, validate, execute) for schema exploration and ad-hoc query testing; minification mode reduces token usage with compact notation Configurable authentication via static headers,..." We'll translate

npx skills add https://github.com/apollographql/skills --skill apollo-mcp-server

Apollo MCP Server Guide

Apollo MCP Server exposes GraphQL operations as MCP tools, enabling AI agents to interact with GraphQL APIs through the Model Context Protocol.

Quick Start

Step 1: Install

# Linux / MacOS
curl -sSL https://mcp.apollo.dev/download/nix/latest | sh

# Windows
iwr 'https://mcp.apollo.dev/download/win/latest' | iex

Step 2: Configure

Create config.yaml in your project root:

# config.yaml
transport:
  type: streamable_http
schema:
  source: local
  path: ./schema.graphql
operations:
  source: local
  paths:
    - ./operations/
introspection:
  introspect:
    enabled: true
  search:
    enabled: true
  validate:
    enabled: true
  execute:
    enabled: true

Start the server:

apollo-mcp-server ./config.yaml

The MCP endpoint is available at http://127.0.0.1:8000/mcp (streamable_http defaults: address 127.0.0.1, port 8000). The GraphQL endpoint defaults to http://localhost:4000/ — override with the endpoint key if your API runs elsewhere.

Step 3: Connect

Add to your MCP client configuration:

Streamable HTTP (recommended):

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "graphql-api": {
      "command": "npx",
      "args": ["mcp-remote", "http://127.0.0.1:8000/mcp"]
    }
  }
}

Claude Code:

claude mcp add graphql-api -- npx mcp-remote http://127.0.0.1:8000/mcp

Stdio (client launches the server directly):

Claude Desktop (claude_desktop_config.json) or Claude Code (.mcp.json):

{
  "mcpServers": {
    "graphql-api": {
      "command": "./apollo-mcp-server",
      "args": ["./config.yaml"]
    }
  }
}

Built-in Tools

Apollo MCP Server provides four introspection tools:

ToolPurposeWhen to Use
introspectExplore schema types in detailNeed type definitions, fields, relationships
searchFind types in schemaLooking for specific types or fields
validateCheck operation validityBefore executing operations
executeRun ad-hoc GraphQL operationsTesting or one-off queries

Defining Custom Tools

MCP tools are created from GraphQL operations. Three methods:

1. Operation Files (Recommended)

operations:
  source: local
  paths:
    - ./operations/

Each file must contain exactly one operation. Each named operation becomes an MCP tool.

# operations/GetUser.graphql
query GetUser($id: ID!) {
  user(id: $id) {
    id
    name
    email
  }
}
# operations/CreateUser.graphql
mutation CreateUser($input: CreateUserInput!) {
  createUser(input: $input) {
    id
    name
  }
}

2. Operation Collections

operations:
  source: collection
  id: your-collection-id

Use GraphOS Studio to manage operations collaboratively.

3. Persisted Queries

operations:
  source: manifest
  path: ./persisted-query-manifest.json

For production environments with pre-approved operations.

Reference Files

Detailed documentation for specific topics:

Key Rules

Security

  • Never expose sensitive operations without authentication
  • Use headers configuration for API keys and tokens
  • Disable introspection tools in production (they are disabled by default)
  • Set overrides.mutation_mode: explicit to require confirmation for mutations

Authentication

# Static header
headers:
  Authorization: "Bearer ${env.API_TOKEN}"

# Dynamic header forwarding
forward_headers:
  - x-forwarded-token

# OAuth (streamable_http transport)
transport:
  type: streamable_http
  auth:
    servers:
      - https://auth.example.com/.well-known/openid-configuration
    audiences:
      - https://api.example.com

Token Optimization

Enable minification to reduce token usage:

introspection:
  introspect:
    minify: true
  search:
    minify: true

Minified output uses compact notation:

  • T = type, I = input, E = enum
  • s = String, i = Int, b = Boolean, f = Float, d = ID
  • ! = required, [] = list

Mutations

Control mutation behavior via the overrides section:

overrides:
  mutation_mode: all       # Execute mutations directly
  # mutation_mode: explicit  # Require explicit confirmation
  # mutation_mode: none      # Block all mutations (default)

Common Patterns

GraphOS Cloud Schema

# schema.source defaults to uplink — can be omitted when graphos is configured
graphos:
  apollo_key: ${env.APOLLO_KEY}
  apollo_graph_ref: my-graph@production

Local Development

transport:
  type: streamable_http
schema:
  source: local
  path: ./schema.graphql
introspection:
  introspect:
    enabled: true
  search:
    enabled: true
  validate:
    enabled: true
  execute:
    enabled: true
overrides:
  mutation_mode: all

Production Setup

transport:
  type: streamable_http
endpoint: https://api.production.com/graphql
operations:
  source: manifest
  path: ./persisted-query-manifest.json
graphos:
  apollo_key: ${env.APOLLO_KEY}
  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}
headers:
  Authorization: "Bearer ${env.API_TOKEN}"
health_check:
  enabled: true

Docker

transport:
  type: streamable_http
  address: 0.0.0.0
  port: 8000
endpoint: ${env.GRAPHQL_ENDPOINT}
graphos:
  apollo_key: ${env.APOLLO_KEY}
  apollo_graph_ref: ${env.APOLLO_GRAPH_REF}
health_check:
  enabled: true

Ground Rules

  • ALWAYS configure authentication before exposing to AI agents
  • ALWAYS use mutation_mode: explicit or mutation_mode: none in shared environments
  • NEVER expose introspection tools with write access to production data
  • PREFER operation files over ad-hoc execute for predictable behavior
  • PREFER streamable_http transport for remote and multi-client deployments
  • USE stdio only when the MCP client launches the server process directly
  • USE GraphOS Studio collections for team collaboration

Plus de skills de apollographql

apollo-federation
apollographql
Apollo Federation permet de composer plusieurs API GraphQL (sous-graphes) en un super
apollo-ios
apollographql
Apollo iOS est un client GraphQL fortement typé pour les plateformes Apple. Il génère des types Swift à partir de vos opérations et schémas GraphQL, et fournit un client async/await, un cache normalisé (en mémoire ou basé sur SQLite), un transport HTTP basé sur des intercepteurs pluggables qui gère les requêtes, mutations et abonnements multipart, ainsi qu'un transport WebSocket optionnel (graphql-transport-ws) pouvant prendre en charge tout type d'opération.
apollo-router
apollographql
Apollo Router est un routeur de graphes haute performance écrit en Rust pour exécuter les supergraphes Apollo Federation 2. Il se place devant vos sous-graphes et gère la planification des requêtes, l'exécution et la composition des réponses.
apollo-router-plugin-creator
apollographql
Créez des plugins Rust natifs pour Apollo Router.
apollo-server
apollographql
Guide complet pour construire des serveurs GraphQL avec Apollo Server 5.x à travers différents frameworks. Couvre la définition de schéma, les résolveurs, la configuration du contexte et la gestion des erreurs avec le support TypeScript. Prend en charge le mode autonome pour le prototypage et les intégrations avec Express, Fastify, Koa et les environnements serverless. Inclut les modèles de résolveurs, l'authentification/autorisation, les plugins, DataLoader pour la prévention N+1 et les techniques d'optimisation des performances. Fournit une documentation de référence pour les sources de données, les erreurs...
graphql-operations
apollographql
Guide des bonnes pratiques pour rédiger des opérations GraphQL efficaces et typées en toute sécurité, et les organiser avec des fragments. Couvre les requêtes, mutations, souscriptions et fragments avec conventions de nommage, syntaxe des variables et utilisation des directives. Met l'accent sur les principes fondamentaux : ne demander que les champs nécessaires, nommer toutes les opérations, utiliser des variables au lieu de valeurs codées en dur, et inclure les champs d'identifiant pour la mise en cache. Recommande de colocaliser les fragments avec les composants et d'utiliser les directives @include / @skip pour les champs conditionnels...
graphql-schema
apollographql
Guide des meilleures pratiques industrielles pour concevoir des schémas GraphQL intuitifs, performants et maintenables. Couvre les principes de conception fondamentaux, notamment l'organisation des types centrée sur le client, les modèles de nullabilité explicite et les stratégies d'évolution rétrocompatibles. Fournit une documentation de référence sur les types, les conventions de nommage, la pagination basée sur curseur, la modélisation des erreurs et les considérations de sécurité. Inclut des modèles pratiques pour les interfaces, les unions, les types d'entrée, les mutations et les stratégies d'identifiant avec des exemples de code...
rover
apollographql
We need to translate the given text from English to French, preserving the name "rover" and other technical terms. The text describes the Apollo Rover CLI. We must not include the name unless it appears in the source text. The source text includes "rover" in "Apollo Rover CLI" and "rover dev command". So we keep "rover" as is. Also preserve "GraphQL", "federation", "supergraph", "GraphOS", "CI/CD", "JSON", etc. Translate the rest naturally. Let's translate: "Apollo Rover CLI for managing GraphQL schemas, federation, and local supergraph development. Publish, fetch, and validate subgraph schemas; compose federated supergraphs locally or via GraphOS Includes schema checking (pre-deploy validation), linting, and introspection from running servers rover dev command starts a local Router with automatic schema composition for development workflows Supports CI/CD patterns with check-before-publish validation and JSON output for scripting Requires..." Translation: "Apollo Rover CLI pour la gestion des schémas Graph