--- title: "Apollo MCP Server: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/apollo/ description: "Exposes a chosen set of GraphQL operations as MCP tools backed by an existing graph." --- # Apollo MCP Server: review, setup & limitations · Undominated.ai > Exposes a chosen set of GraphQL operations as MCP tools backed by an existing graph. [← Explore all mcp servers](/mcp-servers/) DEVELOPMENT WORKFLOW / Apollo GraphQL # Apollo MCP Server Exposes a chosen set of GraphQL operations as MCP tools backed by an existing graph. [See setup guidance ↓](#setup)[Original source ↗](https://www.apollographql.com/docs/apollo-mcp-server/) SOURCE REVIEW Reviewed 2026-10-14 Evidence 4 linked sources Publisher Apollo GraphQL Licence [MIT ↗](https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/LICENSE) Revision 04e4e6e406a7 [Read what was—and wasn’t—checked ↓](#review) “Apollo MCP Server is a Model Context Protocol server that exposes GraphQL operations as MCP tools.” [Apollo GraphQL · upstream description ↗](https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/README.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Allows teams to define the GraphQL operations that become named tools instead of handing over an unrestricted API client. - Documents mutation modes and separate ad-hoc execution settings that make the intended operation boundary reviewable. - The pinned README is Apollo's server for turning configured GraphQL operations into MCP tools in front of a graph. - It does not list the operations itself; those have to be supplied in configuration, which the README points at the user guide for. ### A good fit for - Expose reviewed GraphQL operations as narrowly described tools for a specific graph. - Investigate schema changes against a known operation set before enabling ad hoc queries. - Exposing a chosen set of GraphQL operations to an MCP client in front of an Apollo graph ### Weigh up before choosing - Requires a graph endpoint, operation definitions and configuration; the server alone does not provide a data source. - mutation_mode: none suppresses GraphQL mutations, but is not a universal side-effect guarantee for query resolvers. explicit and all modes broaden that boundary. - Tool annotations and mutation modes do not replace per-user API authorization or approval for consequential actions. - Static header values in configuration are literal strings, not a general environment-substitution mechanism. Inject secrets with the documented runtime mechanisms rather than assuming a placeholder expands. - The configuration file is watched: edits can restart the server and alter exposed capabilities during an ongoing client session. - The pinned README does not document mutation or introspection switches; it defers configuration to the config-file reference. - A Rust toolchain is required only if you build from source with cargo build. - Security vulnerabilities are not meant to be filed as GitHub issues. - A pin does not verify transitive dependencies. - This review did not execute the resource. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - README.md, Cargo.toml and LICENSE - Official installation and configuration reference, including mutation and introspection controls - 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch. - README.md - LICENSE ### Our findings - The documented mutation-mode default is none; ad-hoc execution is a separate option that should remain disabled unless required. - Current publisher configuration docs distinguish predefined mutation exposure from ad hoc execution: explicit permits predefined mutations but rejects ad hoc mutations, while all permits both if execute is enabled. The executable accepts a positional configuration path. - The server exposes GraphQL operations as MCP tools so a model can call APIs running with Apollo. - It will not function until a graph, the operation definitions to expose, a configuration file, and an MCP client are all configured. - This README does not contain that configuration. It says the details are on the user guide, and it says not to open a public GitHub issue for a security vulnerability. ### Not established by this review - No MCP server or upstream package was installed or run. - No authenticated account, client handshake, query, write operation or security test was performed. - No authenticated session, installation, permission bypass or package-to-source parity test was performed. - The server was not started and its tools were not called. - A pin does not verify transitive dependencies. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. [Upstream setup instructions ↗](https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/README.md) - Inspect an official release or build the pinned source with the documented Rust workflow. - Configure the graph endpoint and a reviewed operation allowlist; begin with mutation_mode: none and no ad-hoc execution. - Use stdio locally or protect the HTTP deployment with appropriate authentication, then inspect tools in the intended client. ### Before you start - A GraphQL endpoint and authorized credentials - A reviewed operation set and configuration file - Rust if building from source ### Documented configuration example Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts. { "mcpServers": { "mcp-My API": { "command": "npx", "args": [ "mcp-remote", "http://127.0.0.1:8000/mcp" ] } } } Copy configuration ↗ ### Compatibility MCP clients ### Implementation Rust ### Transports stdio · Streamable HTTP ### Account-scoped MCP integration - Call the configured graph with the configured credentials - Any permitted mutations or side-effecting resolvers act with those credentials ### Cost model MIT-licensed server; graph hosting, GraphOS features and assistant usage may incur separate charges. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Official setup and capabilities ↗](https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/README.md) Checked 2026-10-07 https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/README.md Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review - [Licence at reviewed source revision ↗](https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/LICENSE) Checked 2026-10-07 https://github.com/apollographql/apollo-mcp-server/blob/04e4e6e406a7747e97238dbbea352007c253738e/LICENSE Supports: license, access.cost - [Official server installation ↗](https://www.apollographql.com/docs/apollo-mcp-server/run) Checked 2026-10-14 https://www.apollographql.com/docs/apollo-mcp-server/run Supports: install, compatibility, summary, configExample, access, limitations, bestFor, review, transports - [Configuration and mutation controls ↗](https://www.apollographql.com/docs/apollo-mcp-server/config-file) Checked 2026-10-14 https://www.apollographql.com/docs/apollo-mcp-server/config-file Supports: limitations, review, access, summary, install, configExample, bestFor, compatibility, transports KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Postman MCP ↗ Connects assistants to Postman collections, workspaces and environments through selectable tool sets.](/mcp-servers/postman/)[### Buildkite MCP server ↗ Exposes Buildkite pipelines, builds, jobs, and tests to an MCP client, locally or through Buildkite's remote server.](/mcp-servers/buildkite-mcp-server/)[### CircleCI MCP ↗ Inspects CircleCI pipeline failures and performs explicitly authorized workflow actions through its hosted MCP service.](/mcp-servers/circleci/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Inspect resource evidence](/tools/) - [Choose a host](/agents/) - [Inspect reusable workflows](/skills/) - [Use Undominated data](/api/)