Index of every page on this site: llms.txt
All skills
apollographql avatar

/apollo-mcp-server

@9dda139 official
by Apollo GraphQLapollographql/skills134 stars
14
Run it yourself

Guide for using Apollo MCP Server to connect AI agents with GraphQL APIs. Use this skill when: (1) setting up or configuring Apollo MCP Server, (2) defining MCP tools from GraphQL operations, (3) using introspection tools (introspect, search, validate, execute, explorer), (4) configuring authentication, CORS, health checks, or telemetry, (5) writing Rhai scripts for request lifecycle hooks, (6) defining MCP prompts, (7) troubleshooting MCP server connectivity or tool execution issues, (8) building MCP Apps for interactive UI experiences, (9) deploying Apollo MCP Server to production.

Use this Skill: https://skilld.dev/gh/apollographql/skills/apollo-mcp-server

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprompts.md

≈624 tokens on demand. Your agent reads this file only when SKILL.md points to it.

MCP Prompts

Overview

Apollo MCP Server supports MCP prompts — reusable prompt templates that AI clients can discover and use. Prompts are guided workflows that help AI models use your GraphQL tools more effectively.

No configuration is required. The server automatically detects a prompts/ directory in the working directory and advertises prompt support to MCP clients.

Configuration

Configure the prompts directory in your config file:

prompts:
  path: /config/prompts

The path can be absolute or relative to the process working directory. Defaults to prompts. Set via APOLLO_MCP_PROMPTS__PATH environment variable.

Defining Prompts

Store .md files in a prompts/ directory:

your-project/
├── config.yaml
└── prompts/
    └── check_orders.md

Prompt File Format

Each file has YAML frontmatter and a template body separated by ---:

---
name: check_orders
description: "Look up a user's recent orders and summarize them"
arguments:
  - name: email
    description: "The customer's email address"
    required: true
  - name: limit
    description: "Maximum number of orders to return"
---

1. Use GetUserByEmail(email={{email}}) to find the user
2. Use GetUserOrders to retrieve their recent orders{{limit}}
3. Summarize each order with its status, total, and date

Frontmatter Fields

Field Type Required Description
name string Yes Unique identifier for the prompt
description string No Human-readable description for AI clients
arguments list No Arguments the prompt accepts

Argument Fields

Field Type Default Description
name string — Argument name, used as {{name}} placeholder
description string — Description shown to AI clients
required boolean false Whether the argument must be provided

Template Placeholders

Use {{argument_name}} in the template body. The server replaces each placeholder with the value provided in a prompts/get request. Unmatched placeholders remain unchanged.

Behavior

  • If the prompts/ directory does not exist, the server starts normally without prompt support
  • Required arguments are validated; missing ones return an error
  • Each prompt returns a single user-role text message
  • Multi-message and non-text content types are not currently supported

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert23d5 checks · Risk HIGH
  • Gen Agent Trust Hub23d

    This skill provides a comprehensive guide for using the Apollo MCP Server. It includes official installation commands that download and execute scripts from the vendor's domain. The skill also processes external GraphQL data, such as schemas and operations, which presents a surface for indirect prompt injection if these sources are attacker-controlled. Additionally, it documents the use of Rhai scripting for runtime customization of server behavior.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: LOW · No issues

  • Runlayer8mo

    2/4 files flagged

  • ZeroLeaks7mo

    1 finding · Score: 82/100

Signed by skilld at 9dda139. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago
What it can do
Runs commands
compatibility
Works with Claude Code, Claude Desktop, Cursor.
metadata
{
  "author": "apollographql",
  "version": "1.3.0"
}
All 1 allowed tools
Bash(rover:*) Bash(npx:*) Read Write Edit Glob Grep
  • MCP
  • API
  • graphql
  • apollo
  • introspection
  • schema
  • claude
  • cursor
  • authentication

README badge

README badge for apollographql/skills/apollo-mcp-server

Exposes GraphQL operations as MCP tools, allowing AI agents to query and mutate GraphQL APIs through the Model Context Protocol. Includes introspection tools (search, validate, execute) and supports operation files, GraphOS collections, and persisted queries with configurable authentication and mutation controls.

Generated from the current SKILL.md.

What transport types does Apollo MCP Server support?
Apollo MCP Server supports streamable_http (recommended for remote and multi-client deployments) and stdio (for clients that launch the server directly). Streamable_http defaults to address 127.0.0.1 and port 8000.
Can I use this with Claude Desktop and Claude Code?
Yes. Apollo MCP Server is compatible with Claude Desktop, Claude Code, and Cursor. Configuration differs slightly: Claude Desktop uses claude_desktop_config.json, while Claude Code uses .mcp.json or the claude mcp add command.
How do I define custom tools from GraphQL operations?
Create GraphQL operation files in a directory (one operation per file) and configure the operations source as local with the directory path. Each named operation automatically becomes an MCP tool. You can also use GraphOS Studio collections or persisted query manifests.
What security settings should I enable for production?
Set mutation_mode to explicit or none (default), use headers configuration for API keys, enable health checks, disable introspection tools, and authenticate requests with Bearer tokens or OAuth. Use persisted queries instead of ad-hoc operations.
What are the four built-in introspection tools?
introspect (explore schema types), search (find types in schema), validate (check operation validity), and execute (run ad-hoc GraphQL operations). All four are disabled by default and must be explicitly enabled in config.yaml.

Generated from the current SKILL.md. These answers refresh after source changes.