# GraphOS MCP Tools (remote · mcp.apollographql.com)

Search Apollo docs, specs, and best practices

- Trust score: 70/100 (medium)
- Change this week: +8
- Registry status: deleted
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

> **Deleted**: this server was marked deleted in the MCP registry on 2026-08-03. Its details are retained for reference.

## Components

- remote · `mcp.apollographql.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp.md), [page](https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp)

## Channel facts

- Endpoint: `https://mcp.apollographql.com`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.9.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1925 tokens (~148/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http apollographql-graphos-mcp-tools https://mcp.apollographql.com/
```

### Codex

```toml
[mcp_servers.apollographql-graphos-mcp-tools]
url = "https://mcp.apollographql.com/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "apollographql-graphos-mcp-tools": {
      "type": "remote",
      "url": "https://mcp.apollographql.com/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add apollographql-graphos-mcp-tools --url https://mcp.apollographql.com/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  apollographql-graphos-mcp-tools:
    url: "https://mcp.apollographql.com/"
```

### Other

```json
{
  "mcpServers": {
    "apollographql-graphos-mcp-tools": {
      "type": "http",
      "url": "https://mcp.apollographql.com/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 2.

### 2026-07-31 (score 69, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (13)

### `GetTopOperations` (~269 tokens)

Identify the most-used operations on a graph variant for a time range, with request counts, types, and signatures. Use to find high-traffic operations, detect unused operations, and prioritize findings by traffic impact. Provide graph ID, variant, and a from/to time range (ISO 8601 timestamps; `to` must be at least 6 hours before now), plus an optional limit (default 50). This report is rate limited.

Input parameters:

- `from` (required): The starting timestamp for the report. - Must be in the format: 2025-01-01T00:00:00Z (ISO 8601).   - Must be within the last 549 days.   - The duration between 'from' and 'to' must not exceed 31 day…
- `graphId` (string, required)
- `limit` (integer, required): Maximum number of records to return (default: 10)
- `to` (required): The ending timestamp for the report. - Must be in the format: 2025-01-01T08:00:00Z (ISO 8601). - Must be at least 6 hours from the current time.   - The duration between 'from' and 'to' must not exc…
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetPersistedQueryListStatus` (~79 tokens)

Check whether a graph variant has a Persisted Query List (PQL) and its current build (revision and operation count). Use to assess PQL configuration — a production variant with no PQL is a security gap. Provide the graph ID and variant name.

Input parameters:

- `graphId` (string, required)
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetLaunchHistory` (~110 tokens)

Retrieve recent launches for a graph variant (most recent first) to detect deployment instability such as repeated failures or frequent superseded launches. Each entry includes the launch id, status, and timestamps, so you can identify a specific launch and drill into it with GetLaunch. Use to assess deployment stability. Provide the graph ID, variant name, and optionally a limit (default 20 most recent launches).

Input parameters:

- `graphId` (string, required)
- `limit` (integer, required)
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `ApolloConnectorsSpec` (~33 tokens)

Returns the Apollo Connectors specification for guidance on creating or modifying GraphQL schemas that use @connect or @source.

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetLaunch` (~99 tokens)

Inspect a single launch by ID for full detail: status, timestamps, which subgraphs changed, composition errors, and the schema diff summary. Use to drill into a specific launch — e.g. a failed or superseded one found via GetLaunchHistory (pass its id here). Provide the graph ID, variant name, and launch ID.

Input parameters:

- `graphId` (string, required)
- `launchId` (string, required)
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetSubgraphMetrics` (~291 tokens)

Top subgraphs/connectors by traffic/health for a graph over a time window, as compact CSV (header row + one row per subgraph per day). Columns: start timestamp, end exclusive timestamp, fetch service name, fetch count, fetch latency p50 ms, fetch latency p99 ms, fetch with errors count. Ranked by `orderBy` descending: default FETCH_COUNT (busiest); use FETCH_WITH_ERRORS_COUNT for most error-prone, FETCH_LATENCY_P99_MS for slowest. Rows are per-DAY buckets, so for a multi-day window sum a column per subgraph to get the window total. `variantName` optionally scopes to one or more variants (omit for all). Note: `to` must be at least 1 day in the past (DAY resolution).

Input parameters:

- `from` (required): The starting timestamp for the report. Must be in the format: 2025-01-01T00:00:00Z (ISO 8601).
- `graphId` (string, required)
- `limit` (integer): Maximum number of records to return (default: 100, max 10000).
- `orderBy`
- `to` (required): The ending timestamp for the report. Must be in the format: 2025-01-01T08:00:00Z (ISO 8601).
- `variantName` (array)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetMyIdentity` (~102 tokens)

Resolve the caller's identity from their API key. Call this FIRST when the user asks about "my graph" but has not provided a graph ID. For a graph/service key, `me` resolves to a Graph: use `id` as the graphId and `variants[].name` as the variant for the graph-scoped health-check tools, so the user does not have to supply either. Also handles user keys (memberships) and service-account keys.

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `ApolloDocsRead` (~70 tokens)

Reads an Apollo documentation page by slug in chunks. Use slugs returned by ApolloDocsSearch.

Input parameters:

- `chunkIndex` (integer, required): The character index to start reading from, will return up to the next 10000 characters
- `slug` (string, required): The slug returned from the ApolloDocsSearch tool

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetOperationMetrics` (~284 tokens)

Top operations by usage/health for a graph over a time window, as compact CSV (header row + one row per operation per day). Columns: start timestamp, end exclusive timestamp, operation name, request count, request latency p50 ms, request latency p99 ms, request with error count. Ranked by `orderBy` descending: default REQUEST_COUNT (busiest); use REQUEST_WITH_ERROR_COUNT for most error-prone, REQUEST_LATENCY_P99_MS for slowest. Rows are per-DAY buckets, so for a multi-day window sum a column per operation to get the window total. `variantName` optionally scopes to one or more variants (omit for all). Note: `to` must be at least 1 day in the past (DAY resolution).

Input parameters:

- `from` (required): The starting timestamp for the report. Must be in the format: 2025-01-01T00:00:00Z (ISO 8601).
- `graphId` (string, required)
- `limit` (integer): Maximum number of records to return (default: 100, max 10000).
- `orderBy`
- `to` (required): The ending timestamp for the report. Must be in the format: 2025-01-01T08:00:00Z (ISO 8601).
- `variantName` (array)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetLatestLaunch` (~102 tokens)

Inspect the most recent launch for a graph variant: status, completion time, subgraph changes, composition errors, and a schema diff summary vs the previous launch (additions/removals/edits/deprecations plus affected operations). Use to assess schema composition health and the impact of recent schema changes. Also returns the latest approved launch for comparison. Provide the graph ID and variant name.

Input parameters:

- `graphId` (string, required)
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetVariantDetails` (~94 tokens)

Retrieve detailed metadata for a graph variant: federation version, subgraph inventory (names), router status and any pending router version, and the current router configuration (raw YAML). Use this to assess a variant's health — router config gaps, subgraph inventory, and federation version compliance. Provide the graph ID and variant name (e.g., "production").

Input parameters:

- `graphId` (string, required)
- `variant` (string, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `ApolloDocsSearch` (~69 tokens)

Searches official Apollo documentation for GraphQL, GraphOS, Apollo Router, Apollo Client, MCP Server, schema design, deployment, and Connectors. Returns URLs, slugs, and excerpts.

Input parameters:

- `query` (string, required): Use terms that would lead to broad result with a maximum of 2 keywords.

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

### `GetLintResults` (~93 tokens)

Retrieve schema lint violations from a graph's most recent check workflows: each diagnostic's coordinate, severity level, message, rule, and source location, plus error/warning/total/ignored counts. Use to assess schema quality and naming/best-practice violations. Provide the graph ID and optionally a limit (default 5 most recent check workflows).

Input parameters:

- `graphId` (string, required)
- `limit` (integer, required)

Output parameters:

- `data` (object)
- `errors` (array)
- `extensions` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://mcp.apollographql.com/
- Repository: https://github.com/apollographql/apollo-mcp-server
- Website: https://www.apollographql.com/docs/graphos/platform/graphos-mcp-tools
- Changelog RSS feed: https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/apollographql-graphos-mcp-tools/mcp