Apollo MCP Server

What Apollo MCP Server does

Apollo MCP Server presents GraphQL operations to AI models through the Model Context Protocol. The operations exposed to an MCP client are defined in the server configuration, allowing a deployment to choose which API actions become available as tools. The server sits in front of a graph and connects to an MCP client such as an LLM application or MCP Inspector.

The tool set also covers Apollo GraphOS administration and development workflows. Agents can inspect and publish schemas, validate operations, review schema checks, work with proposals and contract variants, inspect graph artifacts, query usage metrics, search Apollo documentation, and manage selected organization API-key operations.

How it works

A configured graph supplies the Apollo context, while configured GraphQL operations define the callable API surface. An MCP client connects to the running server and discovers the available tools. GraphOS-oriented tools accept graph, organization, variant, proposal, artifact, or check identifiers as appropriate and return structured results, including schema data, statuses, diagnostics, metrics, or error messages.

Read and write workflows can be combined. For example, an agent can identify the caller with GetMyIdentity, inspect a schema or proposal, run validation or checks, and then publish a change. Several write tools correspond to familiar Rover or GraphOS Studio actions, including graph publishing, subgraph deletion, artifact tagging, contract publishing, and proposal review.

Setup and configuration

Install the latest release from crates.io with:

cargo install --locked apollo-mcp-server

The --locked option uses the dependency versions tested for that release. With Rust available, the repository can also be built with cargo build; the resulting development binary is placed in target/debug.

Before starting the server, configure a graph, the GraphQL operations to expose, and a configuration file describing how the server should run. Then connect it to an MCP client. Apollo documents the runtime options in its user guide and configuration-file reference.

Tools and capabilities

The available tools include:

• GraphQL and schema access through GetGraphSchema, GetSubgraphSchema, GetSupergraphSchema, PublishGraphSchema, PublishSubgraph, and ValidateOperations.
• Schema governance with CreateProposal, PublishProposalRevision, ReviewProposal, UpdateProposalStatus, GetProposal, GetProposals, GetSchemaChecks, GetCheckResults, and GetLintResults.
• GraphOS artifact operations including GetGraphArtifact, GetGraphArtifactTags, TagGraphArtifact, and UntagGraphArtifact.
• Usage analysis through GetClientMetrics, GetOperationMetrics, and GetSubgraphMetrics, which return compact CSV data.
• Contract, connector, and documentation support through GetContractConfig, PublishContract, ApolloConnectorsSpec, ApolloDocsSearch, and ApolloDocsRead.
• Identity and organization administration through GetMyIdentity, GetApiKeys, DeleteApiKey, and GetOfflineLicense.

Limitations and notes

Some operations change GraphOS state or what clients receive. Deleting a subgraph, publishing a schema, changing a contract, tagging an artifact, deleting an API key, or removing an artifact tag should be treated as a potentially disruptive action. DeleteSubgraph supports a dry-run mode for checking composition before removal.

Whole-graph and supergraph schema responses can be very large. For federated graphs, the documented scale can exceed 800,000 characters, so GetSubgraphSchema is preferable when a single subgraph is sufficient. Metrics tools require careful use of resolution and limits: bucketed results can undercount a time window when the limit is too small, while MONTH uses calendar-month labels rather than the requested window.