GraphOS MCP server

GraphOS is a remote MCP server that gives an AI agent 14 tools, among them ApolloConnectorsSpec, ApolloDocsRead, ApolloDocsSearch. It answers at https://mcp.apollographql.com over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 21 October 2026, succeeded.

Status

Answering

Tools

Reliability

6 of 6 checks

Response time

194 ms

Transport

streamable HTTP

Last checked

21 October 2026

Search Apollo docs, specs, and best practices

Description as the publisher wrote it.

The 14 tools GraphOS offers

Tool	What it does
`ApolloConnectorsSpec`	Returns the Apollo Connectors specification for guidance on creating or modifying GraphQL schemas that use @connect or @source.
`ApolloDocsRead`	Reads an Apollo documentation page by slug in chunks. Use slugs returned by ApolloDocsSearch. Inputs: slug, chunkIndex
`ApolloDocsSearch`	Searches official Apollo documentation for GraphQL, GraphOS, Apollo Router, Apollo Client, MCP Server, schema design, deployment, and Connectors. Returns URLs, slugs, and excerpts. Inputs: query
`GetClientMetrics`	Traffic broken down by client for a graph over a time window, as compact CSV. Columns: start timestamp, end exclusive timestamp, client name, client version, operation name, request count, request latency p50 ms, request latency p99 ms, req Inputs: graphId, from, to, resolution, orderBy, variantName
`GetLatestLaunch`	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 ass Inputs: graphId, variant
`GetLaunch`	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 (p Inputs: graphId, variant, launchId
`GetLaunchHistory`	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 sp Inputs: graphId, variant, limit, offset
`GetLintResults`	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/b Inputs: graphId, limit
`GetMyIdentity`	Resolve the caller's identity from their API key or OAuth token. 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[]
`GetOperationMetrics`	Top operations by usage/health for a graph over a time window, as compact CSV. Columns: start timestamp, end exclusive timestamp, operation name, request count, request latency p50 ms, request latency p99 ms, request with error count. Ranke Inputs: graphId, from, to, resolution, orderBy, variantName
`GetPersistedQueryListStatus`	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 Inputs: graphId, variant
`GetSubgraphMetrics`	Top subgraphs/connectors by traffic/health for a graph over a time window, as compact CSV. Columns: start timestamp, end exclusive timestamp, fetch service name, fetch count, fetch latency p50 ms, fetch latency p99 ms, fetch with errors cou Inputs: graphId, from, to, resolution, orderBy, variantName
`GetTopOperations`	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, v Inputs: graphId, variant, from, to, limit
`GetVariantDetails`	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 co Inputs: graphId, variant

Add GraphOS to your AI client

Every block below points at https://mcp.apollographql.com. Pick your client and copy.

Claude Code: one command in your terminal

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

Claude Desktop: claude_desktop_config.json

{
  "mcpServers": {
    "graphos": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.apollographql.com"]
    }
  }
}

Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project

{
  "mcpServers": {
    "graphos": {
      "url": "https://mcp.apollographql.com"
    }
  }
}

VS Code and GitHub Copilot: .vscode/mcp.json

{
  "servers": {
    "graphos": {
      "type": "http",
      "url": "https://mcp.apollographql.com"
    }
  }
}

Zed: Zed settings.json

{
  "context_servers": {
    "graphos": {
      "url": "https://mcp.apollographql.com"
    }
  }
}

Windsurf: ~/.codeium/mcp_config.json

{
  "mcpServers": {
    "graphos": {
      "serverUrl": "https://mcp.apollographql.com"
    }
  }
}

JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON

{
  "mcpServers": {
    "graphos": {
      "url": "https://mcp.apollographql.com"
    }
  }
}

Continue: .continue/mcpServers/neuronto.yaml

name: GraphOS
version: 0.0.1
schema: v1
mcpServers:
  - name: GraphOS
    type: streamable-http
    url: https://mcp.apollographql.com

Gemini CLI: ~/.gemini/settings.json

{
  "mcpServers": {
    "graphos": {
      "httpUrl": "https://mcp.apollographql.com"
    }
  }
}

Codex CLI: MCP server config

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

Warp: MCP servers, + Add, paste JSON

{
  "mcpServers": {
    "graphos": {
      "url": "https://mcp.apollographql.com"
    }
  }
}

Goose: a one-click extension link

goose://extension?url=https%3A%2F%2Fmcp.apollographql.com&type=streamable_http&id=graphos&name=GraphOS

Is GraphOS up right now?

It answered our last check on 21 October 2026 in 194 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to GraphOS

SiteGPT Docs3 tools Cloudflare2 tools RevoGrid DataGrid MCP Pro8 tools OpsLevel0 tools Avalara Developer Documentation0 tools Stack Overflow0 tools

Questions about GraphOS

How many tools does GraphOS have?

14, as returned by the server's own tools/list on 13 September 2026: ApolloConnectorsSpec, ApolloDocsRead, ApolloDocsSearch, GetClientMetrics, GetLatestLaunch, GetLaunch, GetLaunchHistory, GetLintResults, and 6 more.

Is GraphOS down?

It answered our last check on 21 October 2026 in 194 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add GraphOS to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.apollographql.com. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does GraphOS need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.apollographql. Endpoint host: mcp.apollographql.com. ARD identifier: urn:air:io.github.apollographql:mcp:graphos-mcp-server. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.