Add support for raw GraphQL queries
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 62/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github, go, graphql
调研方向
跟踪现有的 list_issues GraphQL 实现和 MCP 工具注册,以了解 GitHub API 调用和参数是如何暴露的。添加支持 query 和可选 variables 的原始 GraphQL 入口,目标是文档中记载的 GraphQL 端点,并验证 queries 和 mutations 是否返回可用的结果。
由索引模型根据 Issue 内容生成。
描述
Feature Request: Raw GraphQL Query Tool
Problem
The current MCP server exposes a rich set of REST-based tools but has no way to execute arbitrary GraphQL queries against the GitHub API. This is a significant gap because several important GitHub operations are only available — or significantly richer — via GraphQL.
A concrete example that motivated this request: resolving pull request review threads requires the PRRT_xxx node ID, which is only returned by GraphQL. With the current MCP server there is no way to resolve review threads programmatically, even though pull_request_review_write supports the resolve_thread method and accepts a threadId.
Proposed Solution
Add a graphql tool that executes a raw GraphQL query or mutation against https://api.github.com/graphql, e.g.:
{
"name": "graphql",
"description": "Execute a raw GraphQL query or mutation against the GitHub API.",
"parameters": {
"query": "string — the GraphQL query or mutation",
"variables": "object (optional) — variables to pass to the query"
}
}
Use Cases
- Fetching pull request review thread node IDs (
PRRT_xxx) to resolve threads - Querying
suggestedActorsto discover the Copilot bot handle before assigning - Using
assignCopilotToIssuemutation (currently only available via GraphQL) - Any operation that returns richer data via GraphQL than the equivalent REST endpoint
Notes
- The existing
list_issuestool already uses GraphQL under the hood, so the infrastructure is there - A raw query tool would unlock the full GitHub GraphQL API surface without requiring a new dedicated tool for every GraphQL-only feature
Thanks for the great work on the MCP server!
- 主要语言
- Go
- 星标
- 33.1k
- 派生
- 5k
- 平均合并
- 2 天 1 小时
- 30 天内合并 PR
- 25
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/github-mcp-server 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
github/github-mcp-server#3235 ·
-
enhancement
难度 1/5 1 小时以内 新手友好度 88/100
github/github-mcp-server#3042 · 2 条评论 ·
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
github/github-mcp-server#3032 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 74/100
github/github-mcp-server#2803 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
github/github-mcp-server#2740 ·
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 75/100
-
🤔 refinement needed
难度 2/5 1-3 小时 新手友好度 75/100
equinor/radix-operator#1979 ·