Skip to content
External endpointresponds

GraphOS MCP Server

Search Apollo docs, specs, and best practices

Endpoint URL
https://mcp.apollographql.com
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
145 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.apollographql/graphos-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
graphos-mcp-server
Version
1.17.0
Capability keys
tools
Tool names
GetTopOperations, GetPersistedQueryListStatus, GetLaunchHistory, ApolloConnectorsSpec, GetLaunch, GetSubgraphMetrics, GetMyIdentity, ApolloDocsRead, GetOperationMetrics, GetLatestLaunch, GetVariantDetails, ApolloDocsSearch, GetLintResults
Instructions excerpt

This hosted GraphOS MCP server exposes two kinds of tools: - Public documentation tools (ApolloDocsSearch, ApolloDocsRead, ApolloConnectorsSpec) that require no authentication. Search the documentation first, then read full pages via the returned slugs. - Graph Health Check tools (for example GetVariantDetails, GetLatestLaunch, GetLintResults) that inspect a specific graph and REQUIRE authentication: the server forwards your `x-api-key` request header to the Apollo Platform API. Use a GraphOS graph/service key for the graph you are inspecting; a personal/user key is not used, and there is no APOLLO_KEY for clients of this hosted server. If a health-check tool fails auth (for example `API_KEY_MISSING_OR_INVALID`) or returns null identity or empty data, the server was likely added without an `x-api-key` header. Re-add it with: `claude mcp add --transport http <name> <url> --header "x-api-key: <your key>"`. The documentation tools work with or without a key.

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 240ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 778ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 226ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 145ms