What is the key difference between MCP Graphql and Wick?

MCP Graphql belongs to the Developer Tools category with local stdio execution, while Wick belongs to the Developer Tools category with local stdio execution.

How do I install MCP Graphql or Wick in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Graphql and Wick free or paid?

MCP Graphql operates under a Free / Open Source model (No auth required). Wick operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Graphql lists 2 tools with 3 views and 408 GitHub stars. Wick lists 6 tools with 5 views and 20 GitHub stars.

Can I use both MCP Graphql and Wick together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Graphql vs Wick

In-depth architectural comparison of the MCP Graphql and Wick MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Graphql

Developer Tools · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Wick

Developer Tools · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose MCP Graphql if you need specialized Developer Tools tools running via a local process. Choose Wick if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Graphql when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: introspect-schema, query-graphql.

Explore MCP Graphql Details

Choose Wick when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: WICK_GROUPS, WICK_GODOT_BIN, WICK_PROJECT_PATH.
Primary tools included: Roslyn-enriched exception telemetry, C# symbol and reference analysis, GDScript and scene tooling.

Feature & Specification Comparison

Specification	MCP Graphql blurrah Developer Tools	Wick buildepicshit Developer Tools
Summary	Model Context Protocol server for GraphQL	⃣ 🏠 🍎 🪟 🐧 - Native C MCP server for Godot Engine — 53 tools across 5 pillars: Roslyn-enriched exception telemetry, scene tree inspection, C symbol navigation, MSBuild orchestration, and GDScript analysis. .NET 10, TCP JSON-RPC bridge, 219 tests.
Category & Scope	Developer Tools

Tools & Capabilities Breakdown

MCP Graphql Tools (2)

introspect-schema

This tool retrieves the GraphQL schema. Use this first if you don't have access to the schema as a resource.

query-graphql

Execute GraphQL queries against the endpoint. By default, mutations are disabled unless `ALLOW_MUTATIONS` is set to `true`.

Wick Tools (6)

Roslyn-enriched exception telemetry

C# symbol and reference analysis

GDScript and scene tooling

Runtime launch, logging, and diagnosis

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Graphql Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "blurrah-mcp-graphql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-graphql"
      ]
    }
  }
}

Wick Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "buildepicshit-wick": {
      "command": "npx",
      "args": [
        "-y",
        "buildepicshit-wick"
      ],
      "env": {
        "WICK_GROUPS": "YOUR_WICK_GROUPS_HERE",
        "WICK_GODOT_BIN": "YOUR_WICK_GODOT_BIN_HERE",
        "WICK_PROJECT_PATH": "YOUR_WICK_PROJECT_PATH_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Graphql is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Wick belongs to Developer Tools using local stdio subprocess. Select MCP Graphql when you need capabilities focused on developer tools and Wick when you require tools for developer tools.

More alternatives to MCP Graphql More alternatives to Wick Developer Tools category hub