Provider hosted
Tools: 13
Developer Tools

GraphOS Tools

Connect your account, then chat with AI to run tools.

GraphOS MCP Tools provides a set of utilities for working with GraphQL APIs, including documentation reading and searching capabilities. It is designed for developers who need to interact with GraphQL services efficiently.

Use in your AI tool

Connect straight to this server’s public endpoint.

Remote MCP URL
https://mcp.apollographql.com

Chat in MCPBundles Studio

This server needs a sign-in. MCPBundles handles that setup once — then chat here with saved access and a log of what ran.

Live tools
Agent guide included

Built by

GraphOS Tools

Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.

Browse all tools
Provider hosted
Tools: 13

Live probe refreshed Sep 14, 2026 · Endpoint host mcp.apollographql.com

AI Skill
SKILL.md

Domain knowledge for GraphOS Tools — workflow patterns, data models, and gotchas for your AI agent.

GraphOS Tools provides essential utilities for working with Apollo's GraphQL ecosystem. This service helps developers navigate Apollo's extensive documentation, understand connector specifications, and efficiently search across Apollo's knowledge base.

Capabilities

Documentation Access: Retrieve complete markdown content from Apollo documentation pages using URL slugs. Access in-depth guides, tutorials, and reference materials for Apollo GraphQL, GraphOS, Apollo Router, and Apollo Client.

Apollo Connectors: Access detailed specifications for implementing Apollo Connectors in GraphQL schemas. Get authoritative guidance on connector patterns, configuration, and best practices.

Documentation Search: Search across the full Apollo documentation ecosystem including GraphQL fundamentals, GraphOS platform features, router configuration, client implementations, and API orchestration strategies.

When to Use

This service excels when you need to:

  • Research Apollo-specific implementations and patterns
  • Find configuration examples for GraphOS or Apollo Router
  • Understand connector specifications for schema design
  • Access the latest Apollo documentation without web browsing

Key Considerations

Documentation content reflects Apollo's current published materials. For the most recent updates or unreleased features, verify against the live Apollo documentation site. Search results prioritize official Apollo sources and may not include community content or third-party integrations.

Tools discovered (13)

  • Apollo Connectors Spec

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

  • Apollo Docs Read

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

  • Get Subgraph Metrics

    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

  • Get Operation Metrics

    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

  • Get Variant Details

    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").

  • Get My Identity

    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.

  • Apollo Docs Search

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

  • Get Launch

    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.

  • Get Launch History

    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, max 100 per page) and an offset to page further back.

  • Get Latest Launch

    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.

  • Get Lint Results

    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).

  • Get Top Operations

    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.

  • Get Persisted Query List Status

    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.

Frequently Asked Questions

What is the GraphOS Tools MCP server?

GraphOS MCP Tools provides a set of utilities for working with GraphQL APIs, including documentation reading and searching capabilities. It is designed for developers who need to interact with GraphQL services efficiently. It provides MCP tools that your client discovers when it connects (this page may not list every tool name) that AI agents can use through the Model Context Protocol (MCP).

How do I connect GraphOS Tools to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/graphos-mcp-tools-mcp. Authentication is handled automatically.

How many tools does GraphOS Tools provide?

GraphOS Tools is a remote MCP server. The live tool list is supplied by the server when your MCP client connects, so the count is not fixed on this public page. After you connect in MCPBundles Studio or your client, you will see the tools your session can call. A SKILL.md is still included to guide your agent on capabilities and workflows.

What authentication does GraphOS Tools require?

GraphOS Tools uses API Key. GraphOS Tools requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect GraphOS Tools to any MCP client in minutes

Maintain this listing

Operate GraphOS Tools? You can take over the listing's metadata.

Operate GraphOS Tools?

Take over this listing's metadata — name, description, category, logo, website, contact email, and skill content. Verification is a 6-digit code we email to one of the maintainer addresses your server already publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Sign up to claim

Ready to use GraphOS Tools?

Sign in to connect your credentials and start running tools from the chat.