github / github/github-mcp-server

Add optional "jq" field to every MCP tool

未關閉
#1,306 6 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement
主要語言
Go
星號
33k
分支
5k
平均合併
2 天 1 小時
30 天內合併 PR
52

描述

### Describe the feature or problem you’d like to solve

The GitHub MCP has a systematic problem that its delivered results are too "fat", containing too many tokens.

This is chronic and affects almost every single MCP tool. Some particular problems are
* Getting actions logs results in vast logs being delivered to model
* Getting all the comments on a long issue or discussion results in too much being delivered to model
* Getting the details of a issue or discussion allows no selective choice of data to deliver to model

### Proposed solution

This is a chronic problem with the MCP architecture. The best solution for the GitHub MCP in particular is to
1. document the schema return type for each tool
2. add an optional jq input parameter to every tool call

Then implement the `jq` filtering/transformation/query over the result. This allows models to dramatically reduce the information selected using the full power of JQuery

### Example prompts or workflows (for tools/toolsets only)

```
Search the actions logs for run 1002032 for ERROR lines
```

```
Download the last 10 lines of the actions logs for run 1002032
```

```
Look if Discussion 11 is closed or open and get its labels. Do not get its body.
```

### Additional context

This could also be done as an MCP->MCP transform. But for GitHub's very widely used MCP I think it's worth doing in-MCP.

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。