Apollo Mcp Server

What it does

The guide describes schema sources, operation-backed tools, introspection and transport configuration. It also discusses prompts and request lifecycle hooks. The key architectural decision is which operations an agent may discover and invoke, rather than simply whether the MCP server starts and answers a health check.

Best for

Teams connecting an agent to an existing GraphQL API through a controlled MCP tool surface.

Tradeoffs and requirements

Introspection and mutation configuration are not per-invocation human approval. Forwarded credentials, CORS and OAuth settings must match the selected transport. A broad GraphQL operation can expose data or effects beyond what its short tool description suggests.

Works with Claude Code, Claude Desktop, Cursor.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/apollographql/skills/tree/9dda1397730370aeb8df4ff8f2015c34c86b5003/skills/apollo-mcp-server --skill apollo-mcp-server

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Remote Shell — review the source context.
• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: Bash(rover:*) Bash(npx:*) Read Write Edit Glob Grep. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

73/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

38/100

38

Originality

80/100

80

Static Safety

0/100

0

Suggested workflow

Choose the transport and authentication model, prefer narrowly defined operations and review each tool’s data access and side effects. Configure schema retrieval and credential forwarding explicitly, then connect a development client using the smallest useful permission set.

How to judge the result

Test discovery, unauthorized requests, read operations and deliberately denied mutations. Inspect the real operation executed for each tool and verify error handling without disclosing tokens or internal stack details. Record transport and permission assumptions alongside the configuration.