GitHub GraphQL API MCP

Created By
wanzunza year ago
A Model Control Protocol (MCP) server for exploring the GitHub GraphQL schema and executing optimized queries. Provides AI assistants with efficient GitHub data retrieval capabilities through GraphQL.
Overview

What is GitHub GraphQL API MCP?

GitHub GraphQL API MCP is a Model Control Protocol (MCP) server designed for exploring the GitHub GraphQL schema and executing optimized queries, enabling efficient data retrieval for AI assistants.

How to use GitHub GraphQL API MCP?

To use the GitHub GraphQL API MCP, clone the repository, install dependencies, configure your GitHub personal access token, and start the server. Connect to the server using an MCP client like Claude AI.

Key features of GitHub GraphQL API MCP?

  • Precise data retrieval with GraphQL queries
  • Reduced token consumption by requesting only necessary fields
  • Self-documenting API schema
  • Bilingual support (English/Chinese)

Use cases of GitHub GraphQL API MCP?

  1. Querying repository information such as name and star count.
  2. Retrieving issue data and user profiles.
  3. Analyzing repository contribution trends and managing issues.
  4. Visualizing contributor networks and assessing project dependencies.

FAQ from GitHub GraphQL API MCP?

  • What is the advantage of using GraphQL over REST?

GraphQL allows for precise data retrieval, reducing unnecessary data transfer and API calls.

  • Do I need a GitHub token to use this project?

Yes, a GitHub personal access token is required to access the GitHub API.

  • Is there support for multiple languages?

Yes, the project supports both English and Chinese.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wanzunz
Star
0
Language
Python
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)

20 hours ago
Gpt Scrambler

2 days ago