
GraphQL Forge
Automatically converts GraphQL APIs into individual MCP tools through schema introspection. Connects AI assistants to GraphQL services like GitHub or Shopify APIs without manual setup.
Automatically converts any GraphQL API into individual tools through schema introspection and intelligent caching, enabling seamless integration with GraphQL-based services like GitHub or Shopify APIs without manual tool definition.
What it does
- Generate MCP tools from GraphQL schemas automatically
- Validate parameters and handle GraphQL errors
- Cache schemas for consistent performance
- Support authenticated GraphQL endpoints
- Query any GraphQL API through introspection
Best for
About GraphQL Forge
GraphQL Forge is a community-built MCP server published by toolprint that provides AI assistants with tools and capabilities via the Model Context Protocol. GraphQL Forge automates tool creation from any GraphQL API, offering seamless integration and intelligent caching for Gi It is categorized under developer tools.
How to install
You can install GraphQL Forge in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
GraphQL Forge is released under the NOASSERTION license.
MCP GraphQL Forge
Quick Install
Alternative Installation Methods
# Via Smithery (recommended)
npx @smithery/cli install @toolprint/mcp-graphql-forge --client claude
# Via npm
npm install -g @toolprint/mcp-graphql-forge
An MCP server that makes GraphQL APIs accessible to AI tools by:
- Automatically generating MCP tools from GraphQL schema introspection
- Validating parameters and handling errors for reliable AI interactions
- Supporting both stdio and HTTP transports for development and production
- Caching schema and field selections for consistent performance
✨ Features
- Tool Generation: Creates MCP tools from GraphQL schema introspection
- Parameter Validation: Multi-layer validation prevents GraphQL errors
- Dual Transport: Supports stdio (AI tools) and HTTP (development/testing)
- Schema Management: Optional pre-introspection and caching
- Authentication: Flexible header configuration for authenticated endpoints [Experimental]
🚀 Getting Started
Note: Docker runtime support is currently a work in progress. For production deployments, we recommend using the TypeScript runtime on platforms like Smithery.
Quick Start with HTTP Mode (Recommended for Development)
-
Start the server:
# Start serving it with the Streamable HTTP transport GRAPHQL_ENDPOINT="https://your-api.com/graphql" npx -y @toolprint/mcp-graphql-forge --transport http --port 3001 -
Connect with MCP Inspector:
# In another terminal, launch the inspector npx @modelcontextprotocol/inspector -
With authentication:
# Using environment variables for configuration export GRAPHQL_ENDPOINT="https://api.github.com/graphql" export GRAPHQL_AUTH_HEADER="Bearer YOUR_TOKEN" npx @toolprint/mcp-graphql-forge --transport http --port 3001 # Or all in one line GRAPHQL_ENDPOINT="https://api.github.com/graphql" GRAPHQL_AUTH_HEADER="Bearer YOUR_TOKEN" npx @toolprint/mcp-graphql-forge --transport http --port 3001
Direct AI Integration (Claude/Cursor)
Create an mcp.json in your project root. This will run it in stdio mode.
{
"mcpServers": {
"mcp-graphql-forge": {
"command": "npx",
"args": [
"-y",
"@toolprint/mcp-graphql-forge"
],
"env": {
"GRAPHQL_ENDPOINT": "https://your-api.com/graphql",
"GRAPHQL_AUTH_HEADER": "Bearer YOUR_TOKEN"
}
}
}
}
Schema Management
-
Pre-generate schema:
# Generate schema without starting server GRAPHQL_ENDPOINT="https://your-api.com/graphql" mcp-graphql-forge introspect # Start server using pre-generated schema mcp-graphql-forge --no-introspection --transport http --port 3001 -
Custom schema location:
# Generate schema in custom location SCHEMA_PATH="./schemas/my-api.json" mcp-graphql-forge introspect # Use custom schema location SCHEMA_PATH="./schemas/my-api.json" mcp-graphql-forge --no-introspection --transport http --port 3001 -
Force schema regeneration:
# Force regenerate schema even if it exists mcp-graphql-forge introspect --force # Regenerate and start server mcp-graphql-forge --force-introspection --transport http --port 3001
Advanced Configuration
# Multiple custom headers
export GRAPHQL_HEADER_X_API_KEY="your-api-key"
export GRAPHQL_HEADER_X_CLIENT_ID="your-client-id"
mcp-graphql-forge --transport http --port 3001
# Development mode with auto-reload on schema changes
mcp-graphql-forge --transport http --port 3001 --watch
🛠️ How It Works
1. Schema Introspection
🗂️ Building field selection cache for all types...
📊 Generated field selections for 44 types
💾 Field selection cache contains 44 full selections and 5 minimal selections
Generated 63 tools from GraphQL schema:
- 30 query tools
- 33 mutation tools
2. Intelligent Tool Generation
For a GraphQL schema like:
type Query {
user(id: ID!): User
articles(filters: ArticleFiltersInput, pagination: PaginationArg): [Article]
}
type Mutation {
createUser(input: CreateUserInput!): User
}
Fast MCP GraphQL automatically generates:
- ✅
query_user- with requiredidparameter validation - ✅
query_articles- with optional filtering and pagination - ✅
mutation_createUser- with input validation and complete field selections
3. Smart Field Selection
Instead of manual GraphQL query construction:
# ❌ Error-prone manual approach
query {
articles {
# Missing required field selections!
author {
# Circular reference issues!
}
}
}
Fast MCP GraphQL generates optimal queries automatically:
# ✅ Auto-generated with full field selections
query articlesOperation($filters: ArticleFiltersInput, $pagination: PaginationArg) {
articles(filters: $filters, pagination: $pagination) {
documentId
title
description
author {
documentId
name
email
articles_connection {
nodes { documentId } # Circular reference handled!
}
}
category {
documentId
name
articles { documentId } # Cached selection reused!
}
}
}
🏗️ Architecture
Caching System
- Type-Level Caching: Each GraphQL type's field selection is computed once and reused
- Circular Reference Resolution: Intelligent detection with minimal field fallbacks
- Consistent Output: Same type always generates identical field selections
Validation Pipeline
- JSON Schema Validation: MCP clients validate parameters before execution
- Server-Side Validation: Prevents execution with missing required parameters
- GraphQL Validation: Final validation at the GraphQL layer
Transport Support
- Stdio Transport: For MCP client integration (default)
- HTTP Transport: RESTful interface with MCP 2025 Streamable HTTP specification
- Session Management: Automatic session handling for HTTP transport
📚 API Reference
CLI Options
mcp-graphql-forge [options]
Options:
--transport <type> Transport type: stdio or http (default: stdio)
--port <number> Port for HTTP transport (default: 3000)
--no-introspection Skip schema introspection (use cached schema)
--version Show version number
--help Show help
Environment Variables
| Variable | Description | Example |
|---|---|---|
GRAPHQL_ENDPOINT | GraphQL API endpoint | https://api.example.com/graphql |
GRAPHQL_AUTH_HEADER | Authorization header | Bearer token123 |
GRAPHQL_HEADER_* | Custom headers | GRAPHQL_HEADER_X_API_KEY=key123 |
SCHEMA_PATH | Schema cache file path | ./schema.json |
PORT | HTTP server port | 3001 |
Generated Tool Schema
Each generated tool follows this pattern:
{
name: "query_user",
description: "Execute GraphQL query: user",
inputSchema: {
type: "object",
properties: {
id: { type: "string" }
},
required: ["id"] // Only truly required parameters
}
}
🧪 Testing
Comprehensive Test Suite
- 40+ Test Cases: Covering all functionality and edge cases
- Real-World Scenarios: Tests against actual GraphQL schemas (Strapi, GitHub, etc.)
- Security Testing: Prototype pollution protection and input validation
- Performance Testing: Cache efficiency and field selection optimization
# Run all tests
npm test
# Run specific test suites
npm test -- src/__tests__/field-selection-cache.test.ts
npm test -- src/__tests__/server-validation.test.ts
npm test -- src/__tests__/graphql-execution.test.ts
# Coverage report
npm run test:coverage
Integration Testing
# Test with real GraphQL endpoints
GRAPHQL_ENDPOINT="https://countries.trevorblades.com/" npm test
# Test caching performance
npm run test:performance
🛡️ Security
Parameter Validation
- Required Parameter Enforcement: Prevents GraphQL variable errors
- Null/Undefined Checking: Validates parameter presence and values
- Prototype Pollution Protection: Uses secure property checking methods
Schema Security
- Input Sanitization: All GraphQL inputs are properly typed and validated
- Circular Reference Protection: Prevents infinite recursion in field selections
- Header Validation: Secure header handling for authentication
🚀 Performance
Benchmarks
- Schema Introspection: ~10ms for typical schemas
- Tool Generation: ~5ms with caching enabled
- Field Selection: Pre-computed and cached for instant access
- Memory Usage: Efficient caching with minimal memory footprint
Optimization Features
- Field Selection Caching: Eliminates redundant field selection computation
- Schema Caching: Optional schema persistence for faster restarts
- Minimal GraphQL Queries: Only requests necessary fields
- Connection Pooling:
README truncated. View full README on GitHub.
Alternatives
Related Skills
Browse all skillsMaster REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.
Modern web development expertise covering React, Node.js, databases, and full-stack architecture. Use when: building web applications, developing APIs, creating frontends, setting up databases, deploying web apps, or when user mentions React, Next.js, Express, REST API, GraphQL, MongoDB, PostgreSQL, or full-stack development.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.