GraphQL MCP Tools

Created By
saewoohana year ago
GraphQL MCP server for AI assistants
Overview

What is GraphQL MCP Tools?

GraphQL MCP Tools is a Model Context Protocol (MCP) server implementation that provides GraphQL API interaction capabilities, enabling AI assistants to interact with GraphQL APIs through standardized tools.

How to use GraphQL MCP Tools?

To use GraphQL MCP Tools, you can execute commands via NPX to set up the server with the desired GraphQL endpoint and configuration options.

Key features of GraphQL MCP Tools?

  • Execute GraphQL queries against any endpoint with customizable options.
  • Retrieve and explore GraphQL schema information.
  • Supports command-line configuration for easy setup.

Use cases of GraphQL MCP Tools?

  1. Integrating AI assistants with various GraphQL APIs.
  2. Automating data retrieval and manipulation through GraphQL queries.
  3. Exploring and understanding GraphQL schemas for better API interaction.

FAQ from GraphQL MCP Tools?

  • Can I use GraphQL MCP Tools with any GraphQL API?

Yes! It is designed to work with any GraphQL API endpoint.

  • Is there a limit on query complexity?

Yes, you can set a maximum allowed query complexity through configuration options.

  • What license is GraphQL MCP Tools under?

It is licensed under the MIT License, allowing free use, modification, and distribution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
saewoohan
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago