Gqai GraphQL + AI

Created By
fotoetiennea year ago
Overview

what is gqai?

gqai is a lightweight proxy that exposes GraphQL operations as Model Context Protocol (MCP) tools for AI models like Claude, Cursor, and ChatGPT. It allows users to define tools using regular GraphQL queries/mutations against their GraphQL backend, automatically generating an MCP server.

how to use gqai?

To use gqai, create a .graphqlrc.yml file to define your GraphQL schema and operations, add your GraphQL operations in .graphql files, and configure gqai in your mcp.json file. Then, run gqai to expose these operations as tools for AI models.

key features of gqai?

  • Define tools using GraphQL operations.
  • Automatically discover operations from .graphqlrc.yml.
  • Tool metadata compatible with OpenAI function calling / MCP.

use cases of gqai?

  1. Exposing GraphQL queries as callable tools for AI models.
  2. Simplifying the integration of GraphQL backends with AI applications.
  3. Enabling AI models to interact with GraphQL APIs seamlessly.

FAQ from gqai?

  • Can gqai work with any GraphQL backend?

Yes! gqai is designed to work with any GraphQL backend as long as you provide the correct schema and operations.

  • Is gqai free to use?

Yes! gqai is open-source and free to use under the MIT license.

  • What programming language is gqai built with?

gqai is built with Go.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fotoetienne
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)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago