Make the built-in research agent's MCP tools configurable
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
描述
### Describe the feature or problem you'd like to solve
Research subagents sometimes need access to mcp servers to be productive
### Proposed solution
Today `definitions/research.agent.yaml` hardcodes tools: to github/* + web/grep/glob/view, so /research can't use my other configured MCP servers (ADO, etc.). Forking the agent /.copilot/agents or .github/agents works but freezes the prompt and misses upstream updates and can't reproduce research command's orchestration/report-export. Please add a setting (e.g. research.additionalTools / research.mcpServers ) to extend the built-in research agent's allowed tools with selected MCP servers, so I keep research behavior + updates while adding my own data sources.
### Example prompts or workflows
_No response_
### Additional context
_No response_
貢獻指南
研究方向
從 definitions/research.agent.yaml 開始,追蹤內建研究代理的硬編碼工具如何載入,以及使用者設定如何處理。新增一個受支援的設定,以選取的 MCP 伺服器擴充允許的工具,同時保留內建研究行為、編排和報告匯出。
由索引模型根據 Issue 內容生成。
評估
- 領域
- ai-infra-agents, tooling
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100