Graphql MCP Toolkit

🚀 mcp-graphql

A Model Context Protocol server that enables LLMs to interact with GraphQL APIs. This implementation provides schema introspection and query execution capabilities, allowing models to dynamically discover and use GraphQL APIs.

🚀 Quick Start

When running mcp-graphql, specify the correct endpoint, and it will automatically attempt to introspect your queries.

Command-line Arguments

💻 Usage Examples

Basic Usage

# Basic usage, used with a local GraphQL server
npx mcp-graphql --endpoint http://localhost:3000/graphql

Using Custom Headers

# Use custom headers
npx mcp-graphql --endpoint https://api.example.com/graphql --headers '{"Authorization":"Bearer token123"}'

Enabling Mutation Operations

# Enable mutation operations
npx mcp-graphql --endpoint http://localhost:3000/graphql --enable-mutations

Using a Local Schema File

# Use a local schema file instead of introspection
npx mcp-graphql --endpoint http://localhost:3000/graphql --schema ./schema.graphql

✨ Features

The server provides two main tools:

1. introspect-schema: This tool retrieves the GraphQL schema. Use this tool first if you don't have access to the schema resources. It will use the local schema file or an introspection query.

2. query-graphql: Execute GraphQL queries against the endpoint. Mutation operations are disabled by default unless --enable-mutations is specified.

📚 Documentation

Resources

• graphql-schema: The server exposes the GraphQL schema as a resource for clients to access. This is the result of a local schema file or an introspection query.

📦 Installation

Installation via Smithery

To automatically install the GraphQL MCP toolkit via Smithery:

npx -y @smithery/cli install mcp-graphql --client claude

Manual Installation

You can manually install it with Claude:

{
  "mcpServers": {
    "mcp-graphql": {
      "command": "npx",
      "args": ["mcp-graphql", "--endpoint", "http://localhost:3000/graphql"]
    }
  }
}

🔧 Technical Details

Security Considerations

Mutations are disabled by default as a security measure to prevent LLMs from modifying your database or service data. Exercise caution when enabling mutation operations in a production environment.

Customizing Your Own Server

This is a very general implementation that allows full introspection and allows users to perform any operation (including mutations). If you need a more specific implementation, it is recommended to create your own MCP and restrict client calls to only input specific query fields and/or variables. You can use this as a reference.