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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago