Mcp Graphql Forge

Created By
toolprinta year ago
Overview

What is MCP GraphQL Forge?

MCP GraphQL Forge is a tool 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.

How to use MCP GraphQL Forge?

To use MCP GraphQL Forge, install it via npm or Smithery, start the server with your GraphQL endpoint, and connect it with the MCP Inspector for testing and development.

Key features of MCP GraphQL Forge?

  • Tool Generation: Automatically creates MCP tools from GraphQL schema introspection.
  • Parameter Validation: Multi-layer validation prevents GraphQL errors.
  • Dual Transport: Supports stdio for AI tools and HTTP for development/testing.
  • Schema Management: Optional pre-introspection and caching for performance.
  • Authentication: Flexible header configuration for authenticated endpoints.

Use cases of MCP GraphQL Forge?

  1. Integrating with various GraphQL APIs like GitHub and Strapi.
  2. Generating tools for e-commerce platforms to manage products and orders.
  3. Creating custom schemas for specific applications.

FAQ from MCP GraphQL Forge?

  • Can MCP GraphQL Forge work with any GraphQL API?

Yes! It can connect to any GraphQL API as long as you provide the correct endpoint and authentication.

  • Is there a recommended installation method?

Yes! Using Smithery is recommended for easier setup.

  • How does parameter validation work?

It uses a multi-layer validation approach to ensure all required parameters are present before executing GraphQL queries.

Server Config

{
  "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"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
toolprint
Star
-
Language
-
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)

2 days ago