Apollo MCP Server

io.github.apollographqlPublished by GitHub account apollographqlv2.1.0Updated Oct 30, 2026

MCP server that exposes GraphQL operations as tools for AI models.

VerifiedSTDIODesktop onlyDatabases Developer Tools

Server details

Identifier: io.github.apollographql/apollo-mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account apollographql for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.apollographql%2Fapollo-mcp-server.svg)](https://sourceweft.com/mcp/io.github.apollographql%2Fapollo-mcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Apollo MCP Server exposes GraphQL operations from an Apollo graph as MCP tools, letting an AI assistant call your APIs through defined queries and mutations.

What you can do: Expose GraphQL operations defined for an Apollo graph as callable MCP tools
Let an assistant orchestrate APIs running with Apollo by invoking those operations
Run as a local stdio server configured by a config file and operation definitions
When to use it: Use it when you have an Apollo GraphQL graph and want an assistant to call specific, pre-defined operations against it as tools rather than writing ad-hoc queries.
Requirements: Runs as a local process over stdio; installable from crates.io with Rust/Cargo or built from source, or run from the published container image. Needs a GraphQL graph to sit in front of, definitions of the operations to expose, a configuration file, and an MCP client connection.

Before you install

Exposed operations can include mutations that change data on your graph, so review which operations are defined as tools. The server sits in front of your APIs, so it inherits their access and data exposure; no authentication is declared in the manifest.

Installation

In SourceWeft

Open Apollo MCP Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[MCP Toplist]

[Apollo Client]

[version] [crates.io] [ci workflow status] [release binaries workflow status] [release container workflow status] [license] [codecov]

Apollo MCP Server

Apollo MCP Server is a Model Context Protocol server that exposes GraphQL operations as MCP tools. It provides a standard way for AI models to access and orchestrate your APIs running with Apollo.

Documentation

See the documentation for full details. This README shows the basics of getting this MCP server running. More details are available on the documentation site.

Installation

You can either build this server from source, if you have Rust installed on your workstation, or you can follow the installation guide.

To install the latest release from crates.io, run:

--locked builds with the same dependency versions that were tested for the release.

To build from this repository instead, run cargo build from its root and the server will be built in the target/debug directory.

Getting started

Follow the quickstart tutorial to get started with this server.

Usage

Full usage of Apollo MCP Server is documented on the user guide. There are a few items that are necessary for this server to function. Specifically, the following things must be configured:

A graph for the MCP server to sit in front of.
Definitions for the GraphQL operations that should be exposed as MCP tools.
A configuration file describing how the MCP server should run.
A connection to an MCP client, such as an LLM or MCP inspector.

These are all described on the user guide. Specific configuration options for the configuration file are documented in the config file reference.

Contributions

Checkout the contributor guidelines for more information.

Licensing

This project is licensed under the MIT License. See the LICENSE file for the full license text.

Security

Refer to our security policy.

[!IMPORTANT]
Do not open up a GitHub issue if a found bug is a security vulnerability, and instead to refer to our security policy.

Source: README.md at commit 84843f7

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v2.1.0LatestOct 29, 2026
v2.0.0Oct 6, 2026
v1.20.0Sep 25, 2026
v1.19.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts