diff --git a/README.md b/README.md index 10d987a..ca4f568 100644 --- a/README.md +++ b/README.md @@ -1,41 +1,47 @@ + +> [!NOTE] +> 本文档由 WeHub 基于上游 README 翻译整理，属于社区翻译，非官方中文文档。 +> [English](./README.en.md) · [原始项目](https://github.com/github/github-mcp-server) · [上游 README](https://github.com/github/github-mcp-server/blob/HEAD/README.md) +> 原作者、版权与许可证归属以原始项目及本仓库 LICENSE 文件为准。 + [![Go Report Card](https://goreportcard.com/badge/github.com/github/github-mcp-server)](https://goreportcard.com/report/github.com/github/github-mcp-server) # GitHub MCP Server -The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions. +GitHub MCP Server 可将 AI 工具直接连接到 GitHub 平台。这使 AI 智能体（agent）、助手和聊天机器人能够读取仓库与代码文件、管理 issue 与 PR、分析代码并自动化工作流，全部通过自然语言交互完成。 -### Use Cases +### 使用场景 -- Repository Management: Browse and query code, search files, analyze commits, and understand project structure across any repository you have access to. -- Issue & PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards. -- CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, manage releases, and get insights into your development pipeline. -- Code Analysis: Examine security findings, review Dependabot alerts, understand code patterns, and get comprehensive insights into your codebase. -- Team Collaboration: Access discussions, manage notifications, analyze team activity, and streamline processes for your team. +- 仓库管理：浏览和查询代码、搜索文件、分析提交，并了解你有权访问的任意仓库的项目结构。 +- Issue 与 PR 自动化：创建、更新和管理 issue 与 pull request。让 AI 协助分类 bug、审查代码变更并维护项目看板。 +- CI/CD 与工作流智能：监控 GitHub Actions 工作流运行、分析构建失败、管理发布，并深入了解你的开发流水线。 +- 代码分析：检查安全发现、审查 Dependabot 告警、理解代码模式，并全面了解你的代码库。 +- 团队协作：访问讨论、管理通知、分析团队活动，并为团队简化流程。 -Built for developers who want to connect their AI tools to GitHub context and capabilities, from simple natural language queries to complex multi-step agent workflows. +面向希望将 AI 工具连接到 GitHub 上下文与能力的开发者，从简单的自然语言查询到复杂的多步骤智能体工作流均可支持。 --- -## Remote GitHub MCP Server +## 远程 GitHub MCP Server [![Install in VS Code](https://img.shields.io/badge/VS_Code-Install_Server-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=github&config=%7B%22type%22%3A%20%22http%22%2C%22url%22%3A%20%22https%3A%2F%2Fapi.githubcopilot.com%2Fmcp%2F%22%7D) [![Install in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install_Server-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=github&config=%7B%22type%22%3A%20%22http%22%2C%22url%22%3A%20%22https%3A%2F%2Fapi.githubcopilot.com%2Fmcp%2F%22%7D&quality=insiders) [![Install in Visual Studio](https://img.shields.io/badge/Visual_Studio-Install_Server-C16FDE?style=flat-square&logo=visualstudio&logoColor=white)](https://aka.ms/vs/mcp-install?%7B%22name%22%3A%22github%22%2C%22gallery%22%3Atrue%2C%22url%22%3A%22https%3A%2F%2Fapi.githubcopilot.com%2Fmcp%2F%22%7D) -The remote GitHub MCP Server is hosted by GitHub and provides the easiest method for getting up and running. If your MCP host does not support remote MCP servers, don't worry! You can use the [local version of the GitHub MCP Server](https://github.com/github/github-mcp-server?tab=readme-ov-file#local-github-mcp-server) instead. +远程 GitHub MCP Server 由 GitHub 托管，是上手运行最简便的方式。如果你的 MCP 宿主不支持远程 MCP 服务器，也不用担心！你可以改用[本地版 GitHub MCP Server](https://github.com/github/github-mcp-server?tab=readme-ov-file#local-github-mcp-server)。 -### Prerequisites +### 前置条件 -1. A compatible MCP host with remote server support (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, etc.) -2. Any applicable [policies enabled](https://github.com/github/github-mcp-server/blob/main/docs/policies-and-governance.md) +1. 支持远程服务器的兼容 MCP 宿主（VS Code 1.101+、Claude Desktop、Cursor、Windsurf 等） +2. 已启用所有适用的[策略](https://github.com/github/github-mcp-server/blob/main/docs/policies-and-governance.md) -### Install in VS Code +### 在 VS Code 中安装 -For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start. Make sure you're using [VS Code 1.101](https://code.visualstudio.com/updates/v1_101) or [later](https://code.visualstudio.com/updates) for remote MCP and OAuth support. +如需快速安装，请使用上方的一键安装按钮。完成该流程后，切换 Agent 模式（位于 Copilot Chat 文本输入框旁），服务器即可启动。请确保你使用的是 [VS Code 1.101](https://code.visualstudio.com/updates/v1_101) 或[更高版本](https://code.visualstudio.com/updates)，以支持远程 MCP 与 OAuth。 -Alternatively, to manually configure VS Code, choose the appropriate JSON block from the examples below and add it to your host configuration: +或者，若要手动配置 VS Code，请从下方示例中选择合适的 JSON 代码块，并将其添加到你的宿主配置中： - - + +
Using OAuthUsing a GitHub PAT
VS Code (version 1.101 or greater)
使用 OAuth使用 GitHub PAT
VS Code（1.101 或更高版本）
@@ -79,34 +85,34 @@ Alternatively, to manually configure VS Code, choose the appropriate JSON block
-### Install in other MCP hosts +### 在其他 MCP 宿主中安装 -- **[Copilot CLI](/docs/installation-guides/install-copilot-cli.md)** - Installation guide for GitHub Copilot CLI -- **[GitHub Copilot in other IDEs](/docs/installation-guides/install-other-copilot-ides.md)** - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot -- **[Claude Applications](/docs/installation-guides/install-claude.md)** - Installation guide for Claude Desktop and Claude Code CLI -- **[Codex](/docs/installation-guides/install-codex.md)** - Installation guide for OpenAI Codex -- **[Cursor](/docs/installation-guides/install-cursor.md)** - Installation guide for Cursor IDE -- **[OpenCode](/docs/installation-guides/install-opencode.md)** - Installation guide for the OpenCode terminal agent -- **[Windsurf](/docs/installation-guides/install-windsurf.md)** - Installation guide for Windsurf IDE -- **[Zed](/docs/installation-guides/install-zed.md)** - Installation guide for Zed editor -- **[Rovo Dev CLI](/docs/installation-guides/install-rovo-dev-cli.md)** - Installation guide for Rovo Dev CLI +- **[Copilot CLI](/docs/installation-guides/install-copilot-cli.md)** - GitHub Copilot CLI 安装指南 +- **[GitHub Copilot in other IDEs](/docs/installation-guides/install-other-copilot-ides.md)** - 在 JetBrains、Visual Studio、Eclipse 和 Xcode 中安装 GitHub Copilot +- **[Claude Applications](/docs/installation-guides/install-claude.md)** - Claude Desktop 与 Claude Code CLI 安装指南 +- **[Codex](/docs/installation-guides/install-codex.md)** - OpenAI Codex 安装指南 +- **[Cursor](/docs/installation-guides/install-cursor.md)** - Cursor IDE 安装指南 +- **[OpenCode](/docs/installation-guides/install-opencode.md)** - OpenCode 终端智能体安装指南 +- **[Windsurf](/docs/installation-guides/install-windsurf.md)** - Windsurf IDE 安装指南 +- **[Zed](/docs/installation-guides/install-zed.md)** - Zed 编辑器安装指南 +- **[Rovo Dev CLI](/docs/installation-guides/install-rovo-dev-cli.md)** - Rovo Dev CLI 安装指南 -> **Note:** Each MCP host application needs to configure a GitHub App or OAuth App to support remote access via OAuth. Any host application that supports remote MCP servers should support the remote GitHub server with PAT authentication. Configuration details and support levels vary by host. Make sure to refer to the host application's documentation for more info. +> **注意：** 每个 MCP 宿主应用都需要配置 GitHub App 或 OAuth App，以支持通过 OAuth 进行远程访问。任何支持远程 MCP 服务器的宿主应用都应支持使用 PAT 认证的远程 GitHub 服务器。配置细节与支持程度因宿主而异。请务必查阅宿主应用的文档以获取更多信息。 -### Configuration +### 配置 -#### Toolset configuration +#### 工具集配置 -See [Remote Server Documentation](docs/remote-server.md) for full details on remote server configuration, toolsets, headers, and advanced usage. This file provides comprehensive instructions and examples for connecting, customizing, and installing the remote GitHub MCP Server in VS Code and other MCP hosts. +有关远程服务器配置、工具集、请求头及高级用法的完整说明，请参阅[远程服务器文档](docs/remote-server.md)。该文件提供了在 VS Code 及其他 MCP 宿主中连接、自定义和安装远程 GitHub MCP Server 的全面说明与示例。 -When no toolsets are specified, [default toolsets](#default-toolset) are used. +未指定工具集时，将使用[默认工具集](#default-toolset)。 -#### Insiders Mode +#### Insiders 模式 -> **Try new features early!** The remote server offers an insiders version with early access to new features and experimental tools. +> **抢先体验新功能！** 远程服务器提供 insiders 版本，可提前访问新功能与实验性工具。 - +
Using URL PathUsing Header
使用 URL 路径使用 Header
@@ -142,15 +148,15 @@ When no toolsets are specified, [default toolsets](#default-toolset) are used.
-See [Remote Server Documentation](docs/remote-server.md#insiders-mode) for more details and examples, and [Insiders Features](docs/insiders-features.md) for a full list of what's available. +更多细节与示例请参阅[远程服务器文档](docs/remote-server.md#insiders-mode)，可用功能完整列表请参阅 [Insiders Features](docs/insiders-features.md)。 #### GitHub Enterprise -##### GitHub Enterprise Cloud with data residency (ghe.com) +##### 带数据驻留的 GitHub Enterprise Cloud（ghe.com） -GitHub Enterprise Cloud can also make use of the remote server. +带数据驻留的 GitHub Enterprise Cloud 也可使用远程服务器。 -Example for `https://octocorp.ghe.com` with GitHub PAT token: +使用 GitHub PAT token 的 `https://octocorp.ghe.com` 示例： ``` { @@ -166,52 +172,52 @@ Example for `https://octocorp.ghe.com` with GitHub PAT token: } ``` -> **Note:** When using OAuth with GitHub Enterprise with VS Code and GitHub Copilot, you also need to configure your VS Code settings to point to your GitHub Enterprise instance - see [Authenticate from VS Code](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom) +> **注意：** 在 VS Code 与 GitHub Copilot 中通过 OAuth 使用 GitHub Enterprise 时，你还需要配置 VS Code 设置以指向你的 GitHub Enterprise 实例——请参阅[从 VS Code 进行身份验证](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/configure-personal-settings/authenticate-to-ghecom) ##### GitHub Enterprise Server -GitHub Enterprise Server does not support remote server hosting. Please refer to [GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)](#github-enterprise-server-and-enterprise-cloud-with-data-residency-ghecom) from the local server configuration. +GitHub Enterprise Server 不支持远程服务器托管。请参阅本地服务器配置中的 [GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)](#github-enterprise-server-and-enterprise-cloud-with-data-residency-ghecom)。 --- -## Local GitHub MCP Server +## 本地 GitHub MCP Server [![Install with Docker in VS Code](https://img.shields.io/badge/VS_Code-Install_Server-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=github&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22-p%22%2C%22127.0.0.1%3A8085%3A8085%22%2C%22-e%22%2C%22GITHUB_OAUTH_CALLBACK_PORT%22%2C%22ghcr.io%2Fgithub%2Fgithub-mcp-server%22%5D%2C%22env%22%3A%7B%22GITHUB_OAUTH_CALLBACK_PORT%22%3A%228085%22%7D%7D) [![Install with Docker in VS Code Insiders](https://img.shields.io/badge/VS_Code_Insiders-Install_Server-24bfa5?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=github&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22-p%22%2C%22127.0.0.1%3A8085%3A8085%22%2C%22-e%22%2C%22GITHUB_OAUTH_CALLBACK_PORT%22%2C%22ghcr.io%2Fgithub%2Fgithub-mcp-server%22%5D%2C%22env%22%3A%7B%22GITHUB_OAUTH_CALLBACK_PORT%22%3A%228085%22%7D%7D&quality=insiders) [![Install with Docker in Visual Studio](https://img.shields.io/badge/Visual_Studio-Install_Server-C16FDE?style=flat-square&logo=visualstudio&logoColor=white)](https://aka.ms/vs/mcp-install?%7B%22name%22%3A%22github%22%2C%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22-p%22%2C%22127.0.0.1%3A8085%3A8085%22%2C%22-e%22%2C%22GITHUB_OAUTH_CALLBACK_PORT%3D8085%22%2C%22ghcr.io%2Fgithub%2Fgithub-mcp-server%22%5D%7D) -### Prerequisites +### 前置条件 -1. To run the server in a container, you will need to have [Docker](https://www.docker.com/) installed. -2. Once Docker is installed, you will also need to ensure Docker is running. The Docker image is available at `ghcr.io/github/github-mcp-server`. The image is public; if you get errors on pull, you may have an expired token and need to `docker logout ghcr.io`. -3. **Authentication.** On github.com you don't need to create anything up front — the one-click buttons above log you in with OAuth on first use (a browser-based flow; the token is kept in memory only). The Docker buttons publish a fixed callback port (`127.0.0.1:8085`) so the container's login callback is reachable. See **[Local Server OAuth Login](docs/oauth-login.md)** for how it works, headless/device-code fallback, and bringing your own OAuth or GitHub App (required for GitHub Enterprise Server and `ghe.com`). +1. 若要在容器中运行服务器，你需要已安装 [Docker](https://www.docker.com/)。 +2. 安装 Docker 后，还需确保 Docker 正在运行。Docker 镜像位于 `ghcr.io/github/github-mcp-server`。该镜像为公开镜像；若拉取时出现错误，可能是 token 已过期，需要 `docker logout ghcr.io`。 +3. **身份验证。** 在 github.com 上，你无需预先创建任何内容——上方的一键按钮会在首次使用时通过 OAuth 登录（基于浏览器的流程；token 仅保存在内存中）。Docker 按钮会发布固定的回调端口（`127.0.0.1:8085`），以便容器内的登录回调可被访问。请参阅 **[本地服务器 OAuth 登录](docs/oauth-login.md)**，了解其工作原理、无界面/设备码（device-code）回退方案，以及如何自带 OAuth 或 GitHub App（GitHub Enterprise Server 和 `ghe.com` 需要此项）。 - Prefer a token? You can still authenticate with a [GitHub Personal Access Token](https://github.com/settings/personal-access-tokens/new) by setting `GITHUB_PERSONAL_ACCESS_TOKEN` instead (it takes precedence over OAuth). The MCP server can use many of the GitHub APIs, so enable the permissions that you feel comfortable granting your AI tools (to learn more about access tokens, please check out the [documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)). + 更喜欢使用 token？你仍可通过设置 `GITHUB_PERSONAL_ACCESS_TOKEN` 来使用 [GitHub Personal Access Token](https://github.com/settings/personal-access-tokens/new) 进行身份验证（其优先级高于 OAuth）。MCP 服务器可使用众多 GitHub API，因此请启用你愿意授予 AI 工具的权限（要了解更多关于访问 token 的信息，请参阅 [文档](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)). -
Handling PATs Securely +
安全处理 PAT -### Environment Variables (Recommended) +### 环境变量（推荐） -To keep your GitHub PAT secure and reusable across different MCP hosts: +为在多个 MCP 主机之间安全、可复用地保存 GitHub PAT： -1. **Store your PAT in environment variables** +1. **将 PAT 存储在环境变量中** ```bash export GITHUB_PAT=your_token_here ``` - Or create a `.env` file: + 或创建 `.env` 文件： ```env GITHUB_PAT=your_token_here ``` -2. **Protect your `.env` file** +2. **保护你的 `.env` 文件** ```bash # Add to .gitignore to prevent accidental commits echo ".env" >> .gitignore ``` -3. **Reference the token in configurations** +3. **在配置中引用 token** ```bash # CLI usage @@ -223,18 +229,18 @@ To keep your GitHub PAT secure and reusable across different MCP hosts: } ``` -> **Note**: Environment variable support varies by host app and IDE. Some applications (like Windsurf) require hardcoded tokens in config files. +> **注意**：各主机应用和 IDE 对环境变量的支持程度不同。部分应用（如 Windsurf）要求在配置文件中硬编码 token。 -### Token Security Best Practices +### Token 安全最佳实践 -- **Minimum scopes**: Only grant necessary permissions - - `repo` - Repository operations - - `read:packages` - Docker image access - - `read:org` - Organization team access -- **Separate tokens**: Use different PATs for different projects/environments -- **Regular rotation**: Update tokens periodically -- **Never commit**: Keep tokens out of version control -- **File permissions**: Restrict access to config files containing tokens +- **最小权限范围**：仅授予必要权限 + - `repo` - 仓库操作 + - `read:packages` - Docker 镜像访问 + - `read:org` - 组织团队访问 +- **分离 token**：为不同项目/环境使用不同的 PAT +- **定期轮换**：定期更新 token +- **切勿提交**：不要将 token 纳入版本控制 +- **文件权限**：限制对包含 token 的配置文件的访问 ```bash chmod 600 ~/.your-app/config.json @@ -242,13 +248,13 @@ To keep your GitHub PAT secure and reusable across different MCP hosts:
-### GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com) +### GitHub Enterprise Server 与带数据驻留的 Enterprise Cloud（ghe.com） -The flag `--gh-host` and the environment variable `GITHUB_HOST` can be used to set -the hostname for GitHub Enterprise Server or GitHub Enterprise Cloud with data residency. +标志 `--gh-host` 和环境变量 `GITHUB_HOST` 可用于设置 +GitHub Enterprise Server 或带数据驻留的 GitHub Enterprise Cloud 的主机名。 -- For GitHub Enterprise Server, prefix the hostname with the `https://` URI scheme, as it otherwise defaults to `http://`, which GitHub Enterprise Server does not support. -- For GitHub Enterprise Cloud with data residency, use `https://YOURSUBDOMAIN.ghe.com` as the hostname. +- 对于 GitHub Enterprise Server，请在主机名前添加 `https://` URI 方案，否则默认使用 `http://`，而 GitHub Enterprise Server 不支持该方案。 +- 对于带数据驻留的 GitHub Enterprise Cloud，请使用 `https://YOURSUBDOMAIN.ghe.com` 作为主机名。 ``` json "github": { @@ -270,19 +276,19 @@ the hostname for GitHub Enterprise Server or GitHub Enterprise Cloud with data r } ``` -## Installation +## 安装 -### Install in GitHub Copilot on VS Code +### 在 VS Code 的 GitHub Copilot 中安装 -For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start. +如需快速安装，请使用上方的一键安装按钮。完成该流程后，切换 Agent 模式（位于 Copilot Chat 文本输入框旁），服务器即可启动。 -More about using MCP server tools in VS Code's [agent mode documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers). +有关在 VS Code 的 agent 模式中使用 MCP 服务器工具的更多信息，请参阅 [agent 模式文档](https://code.visualstudio.com/docs/copilot/chat/mcp-servers). -Install in GitHub Copilot on other IDEs (JetBrains, Visual Studio, Eclipse, etc.) +在 GitHub Copilot 的其他 IDE 中安装（JetBrains、Visual Studio、Eclipse 等） -Add one of the following JSON blocks to your IDE's MCP settings. +将以下 JSON 块之一添加到你 IDE 的 MCP 设置中。 -**Log in with OAuth (no token to create or store).** On github.com the official image already includes the app credentials, so you provide none yourself: it runs a browser-based login on first use and keeps the resulting token **in memory only**. In Docker this needs a fixed callback port published to loopback so the container's login callback is reachable: +**使用 OAuth 登录（无需创建或存储 token）。** 在 github.com 上，官方镜像已包含应用凭据，因此你无需自行提供：首次使用时会运行基于浏览器的登录，并将生成的 token **仅保存在内存中**。在 Docker 中，需要将固定的回调端口发布到 loopback，以便容器内的登录回调可被访问： ```json { @@ -309,9 +315,9 @@ Add one of the following JSON blocks to your IDE's MCP settings. } ``` -See **[Local Server OAuth Login](docs/oauth-login.md)** for the native-binary flow (no fixed port needed), the headless/device-code fallback, GitHub Enterprise Server / `ghe.com`, and bringing your own OAuth or GitHub App. +请参阅 **[本地服务器 OAuth 登录](docs/oauth-login.md)**，了解原生二进制流程（无需固定端口）、无界面/设备码回退方案、GitHub Enterprise Server / `ghe.com`，以及如何自带 OAuth 或 GitHub App。 -**Or authenticate with a Personal Access Token.** Set `GITHUB_PERSONAL_ACCESS_TOKEN` instead (it takes precedence over OAuth): +**或使用个人访问令牌（Personal Access Token）进行身份验证。** 改为设置 `GITHUB_PERSONAL_ACCESS_TOKEN`（其优先级高于 OAuth）： ```json { @@ -344,10 +350,10 @@ See **[Local Server OAuth Login](docs/oauth-login.md)** for the native-binary fl } ``` -Optionally, you can add a similar example (i.e. without the mcp key) to a file called `.vscode/mcp.json` in your workspace. This will allow you to share the configuration with other host applications that accept the same format. +你也可以选择将类似示例（即不含 mcp 键）添加到工作区中名为 `.vscode/mcp.json` 的文件。这样即可与接受相同格式的其他主机应用共享配置。
-Example JSON block without the MCP key included +不含 MCP 键的示例 JSON 块
```json @@ -381,27 +387,26 @@ Optionally, you can add a similar example (i.e. without the mcp key) to a file c
-### Install in Other MCP Hosts +### 在其他 MCP 主机中安装 -For other MCP host applications, please refer to our installation guides: +对于其他 MCP 主机应用，请参阅我们的安装指南： -- **[Copilot CLI](docs/installation-guides/install-copilot-cli.md)** - Installation guide for GitHub Copilot CLI -- **[GitHub Copilot in other IDEs](/docs/installation-guides/install-other-copilot-ides.md)** - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot -- **[Claude Code & Claude Desktop](docs/installation-guides/install-claude.md)** - Installation guide for Claude Code and Claude Desktop -- **[Cursor](docs/installation-guides/install-cursor.md)** - Installation guide for Cursor IDE -- **[Google Gemini CLI](docs/installation-guides/install-gemini-cli.md)** - Installation guide for Google Gemini CLI -- **[OpenCode](docs/installation-guides/install-opencode.md)** - Installation guide for the OpenCode terminal agent -- **[Windsurf](docs/installation-guides/install-windsurf.md)** - Installation guide for Windsurf IDE -- **[Zed](docs/installation-guides/install-zed.md)** - Installation guide for Zed editor +- **[Copilot CLI](docs/installation-guides/install-copilot-cli.md)** - GitHub Copilot CLI 安装指南 +- **[GitHub Copilot in other IDEs](/docs/installation-guides/install-other-copilot-ides.md)** - 在 JetBrains、Visual Studio、Eclipse 和 Xcode 中使用 GitHub Copilot 的安装说明 +- **[Claude Code & Claude Desktop](docs/installation-guides/install-claude.md)** - Claude Code 与 Claude Desktop 安装指南 +- **[Cursor](docs/installation-guides/install-cursor.md)** - Cursor IDE 安装指南 +- **[Google Gemini CLI](docs/installation-guides/install-gemini-cli.md)** - Google Gemini CLI 安装指南 +- **[OpenCode](docs/installation-guides/install-opencode.md)** - OpenCode 终端代理安装指南 +- **[Windsurf](docs/installation-guides/install-windsurf.md)** - Windsurf IDE 安装指南 +- **[Zed](docs/installation-guides/install-zed.md)** - Zed 编辑器安装指南 -For a complete overview of all installation options, see our **[Installation Guides Index](docs/installation-guides)**. +如需全面了解所有安装选项，请参阅我们的 **[安装指南索引](docs/installation-guides)**。 -> **Note:** Any host application that supports local MCP servers should be able to access the local GitHub MCP server. However, the specific configuration process, syntax and stability of the integration will vary by host application. While many may follow a similar format to the examples above, this is not guaranteed. Please refer to your host application's documentation for the correct MCP configuration syntax and setup process. +> **注意：** 任何支持本地 MCP 服务器的宿主应用（host application）都应能访问本地 GitHub MCP 服务器。不过，集成的具体配置流程、语法和稳定性会因宿主应用而异。虽然许多应用可能遵循与上文示例类似的格式，但这并不保证一致。请参阅宿主应用的文档，了解正确的 MCP 配置语法和设置流程。 -### Build from source +### 从源码构建 -If you don't have Docker, you can use `go build` to build the binary in the -`cmd/github-mcp-server` directory, and use the `github-mcp-server stdio` command with the `GITHUB_PERSONAL_ACCESS_TOKEN` environment variable set to your token. To specify the output location of the build, use the `-o` flag. You should configure your server to use the built executable as its `command`. For example: +如果你没有 Docker，可以使用 `go build` 在 `cmd/github-mcp-server` 目录中构建二进制文件，并使用 `github-mcp-server stdio` 命令，同时将 `GITHUB_PERSONAL_ACCESS_TOKEN` 环境变量设置为你的 token。若要指定构建输出位置，请使用 `-o` 标志。你应将服务器配置为使用构建生成的可执行文件作为其 `command`。例如： ```JSON { @@ -419,79 +424,79 @@ If you don't have Docker, you can use `go build` to build the binary in the } ``` -### CLI utilities +### CLI 实用工具 -The `github-mcp-server` binary includes a few CLI subcommands that are helpful for debugging and exploring the server. +`github-mcp-server` 二进制文件包含一些有助于调试和探索服务器的 CLI 子命令。 -- `github-mcp-server tool-search ""` searches tools by name, description, and input parameter names. Use `--max-results` to return more matches. -Example (color output requires a TTY; use `docker run -t` (or `-it`) when running in Docker): +- `github-mcp-server tool-search ""` 可按名称、描述和输入参数名称搜索工具。使用 `--max-results` 可返回更多匹配结果。 +示例（彩色输出需要 TTY；在 Docker 中运行时请使用 `docker run -t`（或 `-it`））： ```bash docker run -it --rm ghcr.io/github/github-mcp-server tool-search "issue" --max-results 5 github-mcp-server tool-search "issue" --max-results 5 ``` -## Tool Configuration +## 工具配置 -The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the `--toolsets` flag. This allows you to control which GitHub API capabilities are available to your AI tools. Enabling only the toolsets that you need can help the LLM with tool choice and reduce the context size. +GitHub MCP Server 支持通过 `--toolsets` 标志启用或禁用特定功能组。这使你能够控制哪些 GitHub API 能力可供 AI 工具使用。仅启用所需 toolset 有助于 LLM 进行工具选择并减少上下文大小。 -_Toolsets are not limited to Tools. Relevant MCP Resources and Prompts are also included where applicable._ +_工具集（toolsets）不仅限于工具（Tools）。在适用情况下，相关的 MCP 资源（Resources）和提示（Prompts）也会一并包含。_ -When no toolsets are specified, [default toolsets](#default-toolset) are used. +未指定 toolset 时，将使用[默认 toolset](#default-toolset)。 -> **Looking for examples?** See the [Server Configuration Guide](./docs/server-configuration.md) for common recipes like minimal setups, read-only mode, and combining tools with toolsets. +> **需要示例？** 请参阅[服务器配置指南](./docs/server-configuration.md)，其中包含常见方案，例如最小化配置、只读模式，以及将 tools 与 toolsets 组合使用。 -#### Specifying Toolsets +#### 指定 Toolsets -To specify toolsets you want available to the LLM, you can pass an allow-list in two ways: +若要指定希望向 LLM 开放的 toolsets，可通过以下两种方式传入允许列表（allow-list）： -1. **Using Command Line Argument**: +1. **使用命令行参数**： ```bash github-mcp-server --toolsets repos,issues,pull_requests,actions,code_security ``` -2. **Using Environment Variable**: +2. **使用环境变量**： ```bash GITHUB_TOOLSETS="repos,issues,pull_requests,actions,code_security" ./github-mcp-server ``` -The environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided. +如果同时提供了环境变量和命令行参数，环境变量 `GITHUB_TOOLSETS` 优先于命令行参数。 -#### Specifying Individual Tools +#### 指定单个 Tools -You can also configure specific tools using the `--tools` flag. Tools can be used independently or combined with toolsets for fine-grained control. +你也可以使用 `--tools` 标志配置特定 tools。tools 可单独使用，也可与 toolsets 组合以实现细粒度控制。 -1. **Using Command Line Argument**: +1. **使用命令行参数**： ```bash github-mcp-server --tools get_file_contents,issue_read,create_pull_request ``` -2. **Using Environment Variable**: +2. **使用环境变量**： ```bash GITHUB_TOOLS="get_file_contents,issue_read,create_pull_request" ./github-mcp-server ``` -3. **Combining with Toolsets** (additive): +3. **与 Toolsets 组合**（累加）： ```bash github-mcp-server --toolsets repos,issues --tools get_gist ``` - This registers all tools from `repos` and `issues` toolsets, plus `get_gist`. + 这将注册 `repos` 和 `issues` toolsets 中的所有 tools，以及 `get_gist`。 -**Important Notes:** +**重要说明：** -- Tools and toolsets can be used together -- Read-only mode takes priority: write tools are skipped if `--read-only` is set, even if explicitly requested via `--tools` -- Tool names must match exactly (e.g., `get_file_contents`, not `getFileContents`). Invalid tool names will cause the server to fail at startup with an error message -- When tools are renamed, old names are preserved as aliases for backward compatibility. See [Tool Renaming](docs/tool-renaming.md) for details. +- tools 和 toolsets 可同时使用 +- 只读模式优先：如果设置了 `--read-only`，写入类 tools 将被跳过，即使通过 `--tools` 显式请求也是如此 +- tool 名称必须完全匹配（例如 `get_file_contents`，而不是 `getFileContents`）。无效的 tool 名称会导致服务器在启动时失败并显示错误信息 +- 当 tools 重命名时，旧名称会作为别名保留以保持向后兼容。详见 [Tool 重命名](docs/tool-renaming.md)。 -### Using Toolsets With Docker +### 在 Docker 中使用 Toolsets -When using Docker, you can pass the toolsets as environment variables: +使用 Docker 时，可将 toolsets 作为环境变量传入： ```bash docker run -i --rm \ @@ -500,9 +505,9 @@ docker run -i --rm \ ghcr.io/github/github-mcp-server ``` -### Using Tools With Docker +### 在 Docker 中使用 Tools -When using Docker, you can pass specific tools as environment variables. You can also combine tools with toolsets: +使用 Docker 时，可将特定 tools 作为环境变量传入。你也可以将 tools 与 toolsets 组合使用： ```bash # Tools only @@ -519,17 +524,17 @@ docker run -i --rm \ ghcr.io/github/github-mcp-server ``` -### Special toolsets +### 特殊 toolsets #### "all" toolset -The special toolset `all` can be provided to enable all available toolsets regardless of any other configuration: +可提供特殊 toolset `all`，以启用所有可用 toolsets，不受其他配置影响： ```bash ./github-mcp-server --toolsets all ``` -Or using the environment variable: +或使用环境变量： ```bash GITHUB_TOOLSETS="all" ./github-mcp-server @@ -537,9 +542,9 @@ GITHUB_TOOLSETS="all" ./github-mcp-server #### "default" toolset -The default toolset `default` is the configuration that gets passed to the server if no toolsets are specified. +默认 toolset `default` 是在未指定任何 toolsets 时传给服务器的配置。 -The default configuration is: +默认配置为： - context - repos @@ -547,29 +552,29 @@ The default configuration is: - pull_requests - users -To keep the default configuration and add additional toolsets: +在保留默认配置的同时添加更多 toolsets： ```bash GITHUB_TOOLSETS="default,stargazers" ./github-mcp-server ``` -### Insiders Mode +### Insiders 模式 -The local GitHub MCP Server offers an insiders version with early access to new features and experimental tools. +本地 GitHub MCP Server 提供 insiders 版本，可抢先体验新功能和实验性 tools。 -1. **Using Command Line Argument**: +1. **使用命令行参数**： ```bash ./github-mcp-server --insiders ``` -2. **Using Environment Variable**: +2. **使用环境变量**： ```bash GITHUB_INSIDERS=true ./github-mcp-server ``` -When using Docker: +使用 Docker 时： ```bash docker run -i --rm \ @@ -578,96 +583,96 @@ docker run -i --rm \ ghcr.io/github/github-mcp-server ``` -### Available Toolsets +### 可用 Toolsets -The following sets of tools are available: +以下工具集可用： | | Toolset | Description | | --- | ----------------------- | ------------------------------------------------------------- | -| person | `context` | **Strongly recommended**: Tools that provide context about the current user and GitHub context you are operating in | -| workflow | `actions` | GitHub Actions workflows and CI/CD operations | -| code-square | `code_quality` | GitHub Code Quality related tools | -| codescan | `code_security` | Code security related tools, such as GitHub Code Scanning | -| copilot | `copilot` | Copilot related tools | +| person | `context` | **强烈建议启用**：提供当前用户及所处 GitHub 上下文相关信息的 tools | +| workflow | `actions` | GitHub Actions 工作流及 CI/CD 操作 | +| code-square | `code_quality` | GitHub Code Quality 相关 tools | +| codescan | `code_security` | 代码安全相关 tools，例如 GitHub Code Scanning | +| copilot | `copilot` | Copilot 相关 tools | | dependabot | `dependabot` | Dependabot tools | -| comment-discussion | `discussions` | GitHub Discussions related tools | -| logo-gist | `gists` | GitHub Gist related tools | -| git-branch | `git` | GitHub Git API related tools for low-level Git operations | -| issue-opened | `issues` | GitHub Issues related tools | -| tag | `labels` | GitHub Labels related tools | -| bell | `notifications` | GitHub Notifications related tools | -| organization | `orgs` | GitHub Organization related tools | -| project | `projects` | GitHub Projects related tools | -| git-pull-request | `pull_requests` | GitHub Pull Request related tools | -| repo | `repos` | GitHub Repository related tools | -| shield-lock | `secret_protection` | Secret protection related tools, such as GitHub Secret Scanning | -| shield | `security_advisories` | Security advisories related tools | -| star | `stargazers` | GitHub Stargazers related tools | -| people | `users` | GitHub User related tools | +| comment-discussion | `discussions` | GitHub Discussions 相关 tools | +| logo-gist | `gists` | GitHub Gist 相关 tools | +| git-branch | `git` | 用于底层 Git 操作的 GitHub Git API 相关 tools | +| issue-opened | `issues` | GitHub Issues 相关 tools | +| tag | `labels` | GitHub Labels 相关 tools | +| bell | `notifications` | GitHub Notifications 相关 tools | +| organization | `orgs` | GitHub Organization 相关 tools | +| project | `projects` | GitHub Projects 相关 tools | +| git-pull-request | `pull_requests` | GitHub Pull Request 相关 tools | +| repo | `repos` | GitHub Repository 相关 tools | +| shield-lock | `secret_protection` | 密钥保护相关 tools，例如 GitHub Secret Scanning | +| shield | `security_advisories` | 安全公告相关 tools | +| star | `stargazers` | GitHub Stargazers 相关 tools | +| people | `users` | GitHub User 相关 tools | -### Additional Toolsets in Remote GitHub MCP Server +### 远程 GitHub MCP Server 中的其他工具集 | Toolset | Description | | ----------------------- | ------------------------------------------------------------- | -| `copilot` | Copilot related tools (e.g. Copilot Coding Agent) | -| `copilot_spaces` | Copilot Spaces related tools | -| `github_support_docs_search` | Search docs to answer GitHub product and support questions | +| `copilot` | Copilot 相关工具（例如 Copilot Coding Agent） | +| `copilot_spaces` | Copilot Spaces 相关工具 | +| `github_support_docs_search` | 搜索文档以回答 GitHub 产品与支持问题 | -## Tools +## 工具
workflow Actions -- **actions_get** - Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts) - - **Required OAuth Scopes**: `repo` - - `method`: The method to execute (string, required) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `resource_id`: The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID: - - Provide a workflow ID or workflow file name (e.g. ci.yaml) for 'get_workflow' method. - - Provide a workflow run ID for 'get_workflow_run', 'get_workflow_run_usage', and 'get_workflow_run_logs_url' methods. - - Provide an artifact ID for 'download_workflow_run_artifact' method. - - Provide a job ID for 'get_workflow_job' method. - (string, required) +- **actions_get** - 获取 GitHub Actions 资源（工作流、工作流运行、作业和构件）的详情 + - **必需的 OAuth 作用域**：`repo` + - `method`：要执行的方法（string，必填） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） + - `resource_id`：资源的唯一标识符。该值会因所提供的 "method" 而异，因此请确保提供正确的 ID： + - 对于 `get_workflow` 方法，请提供工作流 ID 或工作流文件名（例如 `ci.yaml`）。 + - 对于 `get_workflow_run`、`get_workflow_run_usage` 和 `get_workflow_run_logs_url` 方法，请提供工作流运行 ID。 + - 对于 `download_workflow_run_artifact` 方法，请提供构件 ID。 + - 对于 `get_workflow_job` 方法，请提供作业 ID。 + （string，必填） -- **actions_list** - List GitHub Actions workflows in a repository - - **Required OAuth Scopes**: `repo` - - `method`: The action to perform (string, required) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (default: 1) (number, optional) - - `per_page`: Results per page for pagination (default: 30, max: 100) (number, optional) - - `repo`: Repository name (string, required) - - `resource_id`: The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID: - - Do not provide any resource ID for 'list_workflows' method. - - Provide a workflow ID or workflow file name (e.g. ci.yaml) for 'list_workflow_runs' method, or omit to list all workflow runs in the repository. - - Provide a workflow run ID for 'list_workflow_jobs' and 'list_workflow_run_artifacts' methods. - (string, optional) - - `workflow_jobs_filter`: Filters for workflow jobs. **ONLY** used when method is 'list_workflow_jobs' (object, optional) - - `workflow_runs_filter`: Filters for workflow runs. **ONLY** used when method is 'list_workflow_runs' (object, optional) +- **actions_list** - 列出仓库中的 GitHub Actions 工作流 + - **必需的 OAuth 作用域**：`repo` + - `method`：要执行的操作（string，必填） + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（默认：1）（number，可选） + - `per_page`：每页结果数（默认：30，最大：100）（number，可选） + - `repo`：仓库名称（string，必填） + - `resource_id`：资源的唯一标识符。该值会因所提供的 "method" 而异，因此请确保提供正确的 ID： + - 对于 `list_workflows` 方法，请勿提供任何资源 ID。 + - 对于 `list_workflow_runs` 方法，请提供工作流 ID 或工作流文件名（例如 `ci.yaml`），或省略以列出仓库中的所有工作流运行。 + - 对于 `list_workflow_jobs` 和 `list_workflow_run_artifacts` 方法，请提供工作流运行 ID。 + （string，可选） + - `workflow_jobs_filter`：工作流作业的筛选条件。**仅**在 method 为 `list_workflow_jobs` 时使用（object，可选） + - `workflow_runs_filter`：工作流运行的筛选条件。**仅**在 method 为 `list_workflow_runs` 时使用（object，可选） -- **actions_run_trigger** - Trigger GitHub Actions workflow actions - - **Required OAuth Scopes**: `repo` - - `inputs`: Inputs the workflow accepts. Only used for 'run_workflow' method. (object, optional) - - `method`: The method to execute (string, required) - - `owner`: Repository owner (string, required) - - `ref`: The git reference for the workflow. The reference can be a branch or tag name. Required for 'run_workflow' method. (string, optional) - - `repo`: Repository name (string, required) - - `run_id`: The ID of the workflow run. Required for all methods except 'run_workflow'. (number, optional) - - `workflow_id`: The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method. (string, optional) +- **actions_run_trigger** - 触发 GitHub Actions 工作流操作 + - **必需的 OAuth 作用域**：`repo` + - `inputs`：工作流接受的输入参数。仅用于 `run_workflow` 方法。（object，可选） + - `method`：要执行的方法（string，必填） + - `owner`：仓库所有者（string，必填） + - `ref`：工作流的 Git 引用。引用可以是分支或标签名称。`run_workflow` 方法必填。（string，可选） + - `repo`：仓库名称（string，必填） + - `run_id`：工作流运行的 ID。除 `run_workflow` 外的所有方法均必填。（number，可选） + - `workflow_id`：工作流 ID（数字）或工作流文件名（例如 `main.yml`、`ci.yaml`）。`run_workflow` 方法必填。（string，可选） -- **get_job_logs** - Get GitHub Actions workflow job logs - - **Required OAuth Scopes**: `repo` - - `failed_only`: When true, gets logs for all failed jobs in the workflow run specified by run_id. Requires run_id to be provided. (boolean, optional) - - `job_id`: The unique identifier of the workflow job. Required when getting logs for a single job. (number, optional) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `return_content`: Returns actual log content instead of URLs (boolean, optional) - - `run_id`: The unique identifier of the workflow run. Required when failed_only is true to get logs for all failed jobs in the run. (number, optional) - - `tail_lines`: Number of lines to return from the end of the log (number, optional) +- **get_job_logs** - 获取 GitHub Actions 工作流作业日志 + - **必需的 OAuth 作用域**：`repo` + - `failed_only`：为 true 时，获取由 run_id 指定的工作流运行中所有失败作业的日志。必须提供 run_id。（boolean，可选） + - `job_id`：工作流作业的唯一标识符。获取单个作业日志时必填。（number，可选） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） + - `return_content`：返回实际日志内容而非 URL（boolean，可选） + - `run_id`：工作流运行的唯一标识符。当 failed_only 为 true 以获取运行中所有失败作业日志时必填。（number，可选） + - `tail_lines`：从日志末尾返回的行数（number，可选）
@@ -675,11 +680,11 @@ The following sets of tools are available: code-square Code Quality -- **get_code_quality_finding** - Get code quality finding - - **Required OAuth Scopes**: `repo` - - `findingNumber`: The number of the finding. (number, required) - - `owner`: The owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) +- **get_code_quality_finding** - 获取代码质量发现项 + - **必需的 OAuth 作用域**：`repo` + - `findingNumber`：发现项编号。（number，必填） + - `owner`：仓库所有者。（string，必填） + - `repo`：仓库名称。（string，必填）
@@ -687,24 +692,24 @@ The following sets of tools are available: codescan Code Security -- **get_code_scanning_alert** - Get code scanning alert - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `alertNumber`: The number of the alert. (number, required) - - `owner`: The owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) +- **get_code_scanning_alert** - 获取代码扫描告警 + - **必需的 OAuth 作用域**：`security_events` + - **可接受的 OAuth 作用域**：`repo`、`security_events` + - `alertNumber`：告警编号。（number，必填） + - `owner`：仓库所有者。（string，必填） + - `repo`：仓库名称。（string，必填） -- **list_code_scanning_alerts** - List code scanning alerts - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `owner`: The owner of the repository. (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `ref`: The Git reference for the results you want to list. (string, optional) - - `repo`: The name of the repository. (string, required) - - `severity`: Filter code scanning alerts by severity (string, optional) - - `state`: Filter code scanning alerts by state. Defaults to open (string, optional) - - `tool_name`: The name of the tool used for code scanning. (string, optional) +- **list_code_scanning_alerts** - 列出代码扫描告警 + - **必需的 OAuth 作用域**：`security_events` + - **可接受的 OAuth 作用域**：`repo`、`security_events` + - `owner`：仓库所有者。（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `ref`：要列出结果的 Git 引用。（string，可选） + - `repo`：仓库名称。（string，必填） + - `severity`：按严重程度筛选代码扫描告警（string，可选） + - `state`：按状态筛选代码扫描告警。默认为 open（string，可选） + - `tool_name`：用于代码扫描的工具名称。（string，可选） @@ -712,19 +717,19 @@ The following sets of tools are available: person Context -- **get_me** - Get my user profile - - No parameters required +- **get_me** - 获取我的用户资料 + - 无需参数 -- **get_team_members** - Get team members - - **Required OAuth Scopes**: `read:org` - - **Accepted OAuth Scopes**: `admin:org`, `read:org`, `write:org` - - `org`: Organization login (owner) that contains the team. (string, required) - - `team_slug`: Team slug (string, required) +- **get_team_members** - 获取团队成员 + - **必需的 OAuth 作用域**：`read:org` + - **可接受的 OAuth 作用域**：`admin:org`、`read:org`、`write:org` + - `org`：包含该团队的组织登录名（所有者）。（string，必填） + - `team_slug`：团队 slug（string，必填） -- **get_teams** - Get teams - - **Required OAuth Scopes**: `read:org` - - **Accepted OAuth Scopes**: `admin:org`, `read:org`, `write:org` - - `user`: Username to get teams for. If not provided, uses the authenticated user. (string, optional) +- **get_teams** - 获取团队 + - **必需的 OAuth 作用域**：`read:org` + - **可接受的 OAuth 作用域**：`admin:org`、`read:org`、`write:org` + - `user`：要获取其团队的用户名。如未提供，则使用已认证用户。（string，可选） @@ -732,19 +737,19 @@ The following sets of tools are available: copilot Copilot -- **assign_copilot_to_issue** - Assign Copilot to issue - - **Required OAuth Scopes**: `repo` - - `base_ref`: Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch (string, optional) - - `custom_instructions`: Optional custom instructions to guide the agent beyond the issue body. Use this to provide additional context, constraints, or guidance that is not captured in the issue description (string, optional) - - `issue_number`: Issue number (number, required) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **assign_copilot_to_issue** - 将 Copilot 分配给议题 + - **必需的 OAuth 作用域**：`repo` + - `base_ref`：智能体将从此处开始工作的 Git 引用（例如分支）。如未指定，默认为仓库的默认分支（string，可选） + - `custom_instructions`：可选的自定义指令，用于在议题正文之外引导智能体。可用于提供议题描述中未包含的额外上下文、约束或指导（string，可选） + - `issue_number`：议题编号（number，必填） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **request_copilot_review** - Request Copilot review - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) +- **request_copilot_review** - 请求 Copilot 审查 + - **Required OAuth Scopes**：`repo` + - `owner`：仓库所有者（string，必填） + - `pullNumber`：拉取请求编号（number，必填） + - `repo`：仓库名称（string，必填） @@ -752,22 +757,22 @@ The following sets of tools are available: dependabot Dependabot -- **get_dependabot_alert** - Get dependabot alert - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `alertNumber`: The number of the alert. (number, required) - - `owner`: The owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) +- **get_dependabot_alert** - 获取 Dependabot 警报 + - **Required OAuth Scopes**：`security_events` + - **Accepted OAuth Scopes**：`repo`、`security_events` + - `alertNumber`：警报编号。（number，必填） + - `owner`：仓库所有者。（string，必填） + - `repo`：仓库名称。（string，必填） -- **list_dependabot_alerts** - List dependabot alerts - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional) - - `owner`: The owner of the repository. (string, required) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: The name of the repository. (string, required) - - `severity`: Filter dependabot alerts by severity (string, optional) - - `state`: Filter dependabot alerts by state. Defaults to open (string, optional) +- **list_dependabot_alerts** - 列出 Dependabot 警报 + - **Required OAuth Scopes**：`security_events` + - **Accepted OAuth Scopes**：`repo`、`security_events` + - `after`：分页游标。使用上一次响应中的游标。（string，可选） + - `owner`：仓库所有者。（string，必填） + - `perPage`：分页每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称。（string，必填） + - `severity`：按严重程度筛选 Dependabot 警报（string，可选） + - `state`：按状态筛选 Dependabot 警报。默认为 open（string，可选） @@ -775,52 +780,52 @@ The following sets of tools are available: comment-discussion Discussions -- **discussion_comment_write** - Manage discussion comments - - **Required OAuth Scopes**: `repo` - - `body`: Comment content (required for 'add', 'reply', and 'update' methods) (string, optional) - - `commentNodeID`: The Node ID of the discussion comment (required for 'reply', 'update', 'delete', 'mark_answer', and 'unmark_answer' methods). For 'reply', this is the top-level comment to reply to; GitHub Discussions only support one level of nesting. (string, optional) - - `discussionNumber`: Discussion number (required for 'add' and 'reply' methods) (number, optional) - - `method`: Write operation to perform on a discussion comment. - Options are: - - 'add' - adds a new top-level comment to a discussion. - - 'reply' - replies to a top-level discussion comment (GitHub Discussions only support one level of nesting). - - 'update' - updates an existing discussion comment. - - 'delete' - deletes a discussion comment. - - 'mark_answer' - marks a discussion comment as the answer (Q&A only). - - 'unmark_answer' - unmarks a discussion comment as the answer (Q&A only). - (string, required) - - `owner`: Repository owner (required for 'add' and 'reply' methods) (string, optional) - - `repo`: Repository name (required for 'add' and 'reply' methods) (string, optional) +- **discussion_comment_write** - 管理讨论评论 + - **Required OAuth Scopes**：`repo` + - `body`：评论内容（'add'、'reply' 和 'update' 方法必填）（string，可选） + - `commentNodeID`：讨论评论的 Node ID（'reply'、'update'、'delete'、'mark_answer' 和 'unmark_answer' 方法必填）。对于 'reply'，这是要回复的顶层评论；GitHub Discussions 仅支持一层嵌套。（string，可选） + - `discussionNumber`：讨论编号（'add' 和 'reply' 方法必填）（number，可选） + - `method`：对讨论评论执行的写入操作。 + 选项包括： + - 'add' - 向讨论添加新的顶层评论。 + - 'reply' - 回复顶层讨论评论（GitHub Discussions 仅支持一层嵌套）。 + - 'update' - 更新现有讨论评论。 + - 'delete' - 删除讨论评论。 + - 'mark_answer' - 将讨论评论标记为答案（仅限 Q&A）。 + - 'unmark_answer' - 取消将讨论评论标记为答案（仅限 Q&A）。 + （string，必填） + - `owner`：仓库所有者（'add' 和 'reply' 方法必填）（string，可选） + - `repo`：仓库名称（'add' 和 'reply' 方法必填）（string，可选） -- **get_discussion** - Get discussion - - **Required OAuth Scopes**: `repo` - - `discussionNumber`: Discussion Number (number, required) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **get_discussion** - 获取讨论 + - **Required OAuth Scopes**：`repo` + - `discussionNumber`：讨论编号（number，必填） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **get_discussion_comments** - Get discussion comments - - **Required OAuth Scopes**: `repo` - - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional) - - `discussionNumber`: Discussion Number (number, required) - - `includeReplies`: When true, each top-level comment will include its replies nested within it (up to 100 replies per comment, which is the GitHub API maximum). Defaults to false. (boolean, optional) - - `owner`: Repository owner (string, required) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) +- **get_discussion_comments** - 获取讨论评论 + - **Required OAuth Scopes**：`repo` + - `after`：分页游标。使用上一次响应中的游标。（string，可选） + - `discussionNumber`：讨论编号（number，必填） + - `includeReplies`：为 true 时，每个顶层评论将包含嵌套在内的回复（每个评论最多 100 条回复，这是 GitHub API 的上限）。默认为 false。（boolean，可选） + - `owner`：仓库所有者（string，必填） + - `perPage`：分页每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） -- **list_discussion_categories** - List discussion categories - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name. If not provided, discussion categories will be queried at the organisation level. (string, optional) +- **list_discussion_categories** - 列出讨论分类 + - **Required OAuth Scopes**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称。如未提供，将在组织级别查询讨论分类。（string，可选） -- **list_discussions** - List discussions - - **Required OAuth Scopes**: `repo` - - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional) - - `category`: Optional filter by discussion category ID. If provided, only discussions with this category are listed. (string, optional) - - `direction`: Order direction. (string, optional) - - `orderBy`: Order discussions by field. If provided, the 'direction' also needs to be provided. (string, optional) - - `owner`: Repository owner (string, required) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name. If not provided, discussions will be queried at the organisation level. (string, optional) +- **list_discussions** - 列出讨论 + - **Required OAuth Scopes**：`repo` + - `after`：分页游标。使用上一次响应中的游标。（string，可选） + - `category`：按讨论分类 ID 可选筛选。如提供，则仅列出该分类下的讨论。（string，可选） + - `direction`：排序方向。（string，可选） + - `orderBy`：按字段对讨论排序。如提供，还需同时提供 'direction'。（string，可选） + - `owner`：仓库所有者（string，必填） + - `perPage`：分页每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称。如未提供，将在组织级别查询讨论。（string，可选） @@ -828,28 +833,28 @@ The following sets of tools are available: logo-gist Gists -- **create_gist** - Create Gist - - **Required OAuth Scopes**: `gist` - - `content`: Content for simple single-file gist creation (string, required) - - `description`: Description of the gist (string, optional) - - `filename`: Filename for simple single-file gist creation (string, required) - - `public`: Whether the gist is public (boolean, optional) +- **create_gist** - 创建 Gist + - **Required OAuth Scopes**：`gist` + - `content`：用于简单单文件 Gist 创建的内容（string，必填） + - `description`：Gist 描述（string，可选） + - `filename`：用于简单单文件 Gist 创建的文件名（string，必填） + - `public`：Gist 是否为公开（boolean，可选） -- **get_gist** - Get Gist Content - - `gist_id`: The ID of the gist (string, required) +- **get_gist** - 获取 Gist 内容 + - `gist_id`：Gist 的 ID（string，必填） -- **list_gists** - List Gists - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `since`: Only gists updated after this time (ISO 8601 timestamp) (string, optional) - - `username`: GitHub username (omit for authenticated user's gists) (string, optional) +- **list_gists** - 列出 Gist + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：分页每页结果数（最小 1，最大 100）（number，可选） + - `since`：仅列出在此时间之后更新的 Gist（ISO 8601 时间戳）（string，可选） + - `username`：GitHub 用户名（省略则列出已认证用户的 Gist）（string，可选） -- **update_gist** - Update Gist - - **Required OAuth Scopes**: `gist` - - `content`: Content for the file (string, required) - - `description`: Updated description of the gist (string, optional) - - `filename`: Filename to update or create (string, required) - - `gist_id`: ID of the gist to update (string, required) +- **update_gist** - 更新 Gist + - **Required OAuth Scopes**：`gist` + - `content`：文件内容（string，必填） + - `description`：Gist 的更新描述（string，可选） + - `filename`：要更新或创建的文件名（string，必填） + - `gist_id`：要更新的 Gist ID（string，必填） @@ -857,13 +862,13 @@ The following sets of tools are available: git-branch Git -- **get_repository_tree** - Get repository tree - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (username or organization) (string, required) - - `path_filter`: Optional path prefix to filter the tree results (e.g., 'src/' to only show files in the src directory) (string, optional) - - `recursive`: Setting this parameter to true returns the objects or subtrees referenced by the tree. Default is false (boolean, optional) - - `repo`: Repository name (string, required) - - `tree_sha`: The SHA1 value or ref (branch or tag) name of the tree. Defaults to the repository's default branch (string, optional) +- **get_repository_tree** - 获取仓库树 + - **Required OAuth Scopes**：`repo` + - `owner`：仓库所有者（用户名或组织）（string，必填） + - `path_filter`：用于筛选树结果的可选路径前缀（例如，'src/' 仅显示 src 目录中的文件）（string，可选） + - `recursive`：将此参数设为 true 时，返回树所引用的对象或子树。默认为 false（boolean，可选） + - `repo`：仓库名称（string，必填） + - `tree_sha`：树的 SHA1 值或 ref（分支或标签）名称。默认为仓库的默认分支（string，可选） @@ -871,109 +876,109 @@ The following sets of tools are available: issue-opened Issues -- **add_issue_comment** - Add comment to issue or pull request - - **Required OAuth Scopes**: `repo` - - `body`: Comment content. Required unless reaction is provided. (string, optional) - - `comment_id`: The numeric ID of the issue or pull request comment to react to. Use this for reactions to comments; omit it to react to the issue or pull request itself. Cannot be combined with body. (number, optional) - - `issue_number`: Issue or pull request number to comment on or react to. (number, required) - - `owner`: Repository owner (string, required) - - `reaction`: Emoji reaction to add. Required unless body is provided. (string, optional) - - `repo`: Repository name (string, required) +- **add_issue_comment** - 为 Issue 或拉取请求添加评论 + - **Required OAuth Scopes**：`repo` + - `body`：评论内容。除非提供了 reaction，否则必填。（string，可选） + - `comment_id`：要添加反应的 Issue 或拉取请求评论的数字 ID。用于对评论添加反应；省略则对 Issue 或拉取请求本身添加反应。不能与 body 同时使用。（number，可选） + - `issue_number`：要评论或添加反应的 Issue 或拉取请求编号。（number，必填） + - `owner`：仓库所有者（string，必填） + - `reaction`：要添加的表情符号反应。除非提供了 body，否则必填。（string，可选） + - `repo`：仓库名称（string，必填） -- **get_label** - Get a specific label from a repository +- **get_label** - 从仓库获取指定标签 - **Required OAuth Scopes**: `repo` - - `name`: Label name. (string, required) - - `owner`: Repository owner (username or organization name) (string, required) - - `repo`: Repository name (string, required) + - `name`: 标签名称。(string, required) + - `owner`: 仓库所有者（用户名或组织名）(string, required) + - `repo`: 仓库名称 (string, required) -- **issue_read** - Get issue details +- **issue_read** - 获取 issue 详情 - **Required OAuth Scopes**: `repo` - - `issue_number`: The number of the issue (number, required) - - `method`: The read operation to perform on a single issue. - Options are: - 1. get - Get issue details. Also returns best-effort hierarchy flags (`has_parent`, `has_children`); `parent` and `sub_issues_summary` are optional relationship summaries. - 2. get_comments - Get issue comments. - 3. get_sub_issues - Get sub-issues (children) of the issue. - 4. get_parent - Get the parent issue, if this issue is a sub-issue of another. - 5. get_labels - Get labels assigned to the issue. + - `issue_number`: issue 编号 (number, required) + - `method`: 对单个 issue 执行的读取操作。 + 选项包括： + 1. get - 获取 issue 详情。还会尽力返回层级标志（`has_parent`、`has_children`）；`parent` 和 `sub_issues_summary` 为可选的关系摘要。 + 2. get_comments - 获取 issue 评论。 + 3. get_sub_issues - 获取该 issue 的子 issue（children）。 + 4. get_parent - 若该 issue 是另一个 issue 的子 issue，则获取其父 issue。 + 5. get_labels - 获取分配给该 issue 的标签。 (string, required) - - `owner`: The owner of the repository (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: The name of the repository (string, required) + - `owner`: 仓库所有者 (string, required) + - `page`: 分页页码（最小为 1）(number, optional) + - `perPage`: 每页结果数（最小为 1，最大为 100）(number, optional) + - `repo`: 仓库名称 (string, required) -- **issue_write** - Create or update issue/pull request +- **issue_write** - 创建或更新 issue/pull request - **Required OAuth Scopes**: `repo` - - `assignees`: Usernames to assign to this issue (string[], optional) - - `body`: Issue body content (string, optional) - - `duplicate_of`: Issue number that this issue is a duplicate of. Only used when state_reason is 'duplicate'. (number, optional) - - `issue_fields`: Issue field values to set or clear. Each item requires 'field_name' and exactly one of 'value', 'field_option_name', or 'delete: true'. (object[], optional) - - `issue_number`: Issue number to update (number, optional) - - `labels`: Labels to apply to this issue (string[], optional) - - `method`: Write operation to perform on a single issue. - Options are: - - 'create' - creates a new issue. - - 'update' - updates an existing issue. + - `assignees`: 要分配给该 issue 的用户名 (string[], optional) + - `body`: issue 正文内容 (string, optional) + - `duplicate_of`: 该 issue 所重复的 issue 编号。仅在 state_reason 为 'duplicate' 时使用。(number, optional) + - `issue_fields`: 要设置或清除的 issue 字段值。每项需要 'field_name'，且 'value'、'field_option_name' 或 'delete: true' 三者必居其一。(object[], optional) + - `issue_number`: 要更新的 issue 编号 (number, optional) + - `labels`: 要应用到该 issue 的标签 (string[], optional) + - `method`: 对单个 issue 执行的写入操作。 + 选项包括： + - 'create' - 创建新 issue。 + - 'update' - 更新现有 issue。 (string, required) - - `milestone`: Milestone number (number, optional) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `state`: New state (string, optional) - - `state_reason`: Reason for the state change. Ignored unless state is changed. (string, optional) - - `title`: Issue title (string, optional) - - `type`: Type of this issue. Only use if issue types are enabled for this repository. Use list_issue_types tool to get valid type values for this repository or its owner organization. If the repository doesn't support issue types, omit this parameter. (string, optional) + - `milestone`: 里程碑编号 (number, optional) + - `owner`: 仓库所有者 (string, required) + - `repo`: 仓库名称 (string, required) + - `state`: 新状态 (string, optional) + - `state_reason`: 状态变更原因。除非状态发生变更，否则会被忽略。(string, optional) + - `title`: issue 标题 (string, optional) + - `type`: 该 issue 的类型。仅在该仓库启用了 issue 类型时使用。使用 list_issue_types 工具获取该仓库或其所属组织的有效类型值。若仓库不支持 issue 类型，请省略此参数。(string, optional) -- **list_issue_fields** - List issue fields +- **list_issue_fields** - 列出 issue 字段 - **Required OAuth Scopes (any of)**: `repo`, `read:org` - **Accepted OAuth Scopes**: `admin:org`, `read:org`, `repo`, `write:org` - - `owner`: The account owner of the repository or organization. The name is not case sensitive. (string, required) - - `repo`: The name of the repository. When provided, returns fields for this specific repository (inherited from its organization). When omitted, returns org-level fields directly. (string, optional) + - `owner`: 仓库或组织的账户所有者。名称不区分大小写。(string, required) + - `repo`: 仓库名称。提供时，返回该特定仓库的字段（继承自其组织）。省略时，直接返回组织级字段。(string, optional) -- **list_issue_types** - List available issue types +- **list_issue_types** - 列出可用的 issue 类型 - **Required OAuth Scopes (any of)**: `repo`, `read:org` - **Accepted OAuth Scopes**: `admin:org`, `read:org`, `repo`, `write:org` - - `owner`: The account owner of the repository or organization. (string, required) - - `repo`: The name of the repository. When provided, returns issue types for this specific repository. When omitted, returns org-level issue types directly. (string, optional) + - `owner`: 仓库或组织的账户所有者。(string, required) + - `repo`: 仓库名称。提供时，返回该特定仓库的 issue 类型。省略时，直接返回组织级 issue 类型。(string, optional) -- **list_issues** - List issues +- **list_issues** - 列出 issues - **Required OAuth Scopes**: `repo` - - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional) - - `direction`: Order direction. If provided, the 'orderBy' also needs to be provided. (string, optional) - - `field_filters`: Filter by custom issue field values. Each entry takes a field_name and a value; the server looks up the field and coerces the value to its type (single-select option name, text, number, or YYYY-MM-DD date). (object[], optional) - - `labels`: Filter by labels (string[], optional) - - `orderBy`: Order issues by field. If provided, the 'direction' also needs to be provided. (string, optional) - - `owner`: Repository owner (string, required) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) - - `since`: Filter by date (ISO 8601 timestamp) (string, optional) - - `state`: Filter by state, by default both open and closed issues are returned when not provided (string, optional) + - `after`: 分页游标。使用上一次响应中的 cursor。(string, optional) + - `direction`: 排序方向。若提供此参数，还需提供 'orderBy'。(string, optional) + - `field_filters`: 按自定义 issue 字段值筛选。每项包含 field_name 和 value；服务器会查找该字段并将 value 强制转换为其类型（单选选项名、文本、数字或 YYYY-MM-DD 日期）。(object[], optional) + - `labels`: 按标签筛选 (string[], optional) + - `orderBy`: 按字段对 issues 排序。若提供此参数，还需提供 'direction'。(string, optional) + - `owner`: 仓库所有者 (string, required) + - `perPage`: 每页结果数（最小为 1，最大为 100）(number, optional) + - `repo`: 仓库名称 (string, required) + - `since`: 按日期筛选（ISO 8601 时间戳）(string, optional) + - `state`: 按状态筛选；未提供时默认同时返回 open 和 closed issues (string, optional) -- **search_issues** - Search issues +- **search_issues** - 搜索 issues - **Required OAuth Scopes**: `repo` - - `order`: Sort order (string, optional) - - `owner`: Optional repository owner. If provided with repo, only issues for this repository are listed. (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Search query using GitHub issues search syntax (string, required) - - `repo`: Optional repository name. If provided with owner, only issues for this repository are listed. (string, optional) - - `sort`: Sort field by number of matches of categories, defaults to best match (string, optional) + - `order`: 排序顺序 (string, optional) + - `owner`: 可选的仓库所有者。若与 repo 一并提供，则仅列出该仓库的 issues。(string, optional) + - `page`: 分页页码（最小为 1）(number, optional) + - `perPage`: 每页结果数（最小为 1，最大为 100）(number, optional) + - `query`: 使用 GitHub issues 搜索语法的搜索查询 (string, required) + - `repo`: 可选的仓库名称。若与 owner 一并提供，则仅列出该仓库的 issues。(string, optional) + - `sort`: 按各类别匹配数量排序的字段，默认为最佳匹配 (string, optional) -- **sub_issue_write** - Change sub-issue +- **sub_issue_write** - 变更子 issue - **Required OAuth Scopes**: `repo` - - `after_id`: The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified) (number, optional) - - `before_id`: The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) (number, optional) - - `issue_number`: The number of the parent issue (number, required) - - `method`: The action to perform on a single sub-issue - Options are: - - 'add' - add a sub-issue to a parent issue in a GitHub repository. - - 'remove' - remove a sub-issue from a parent issue in a GitHub repository. - - 'reprioritize' - change the order of sub-issues within a parent issue in a GitHub repository. Use either 'after_id' or 'before_id' to specify the new position. - Writes issue hierarchy. To move a sub-issue to a new parent, use `add` with `replace_parent=true`; there is no writable parent field. + - `after_id`: 子 issue 应排在之后的子 issue ID（应指定 after_id 或 before_id 之一）(number, optional) + - `before_id`: 子 issue 应排在之前的子 issue ID（应指定 after_id 或 before_id 之一）(number, optional) + - `issue_number`: 父 issue 编号 (number, required) + - `method`: 对单个子 issue 执行的操作 + 选项包括： + - 'add' - 在 GitHub 仓库中将子 issue 添加到父 issue。 + - 'remove' - 在 GitHub 仓库中从父 issue 移除子 issue。 + - 'reprioritize' - 在 GitHub 仓库中更改父 issue 内子 issue 的顺序。使用 'after_id' 或 'before_id' 指定新位置。 + 写入 issue 层级关系。若要将子 issue 移动到新的父 issue，请使用 `add` 配合 `replace_parent=true`；没有可写的 parent 字段。 (string, required) - - `owner`: Repository owner (string, required) - - `replace_parent`: When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional) - - `repo`: Repository name (string, required) - - `sub_issue_id`: The ID of the sub-issue to add. ID is not the same as issue number (number, required) + - `owner`: 仓库所有者 (string, required) + - `replace_parent`: 为 true 时，替换子 issue 当前的父 issue。仅与 'add' 方法一起使用。(boolean, optional) + - `repo`: 仓库名称 (string, required) + - `sub_issue_id`: 要添加的子 issue ID。ID 与 issue 编号不同 (number, required) @@ -981,261 +986,261 @@ The following sets of tools are available: tag Labels -- **get_label** - Get a specific label from a repository +- **get_label** - 从仓库获取指定标签 - **Required OAuth Scopes**: `repo` - - `name`: Label name. (string, required) - - `owner`: Repository owner (username or organization name) (string, required) - - `repo`: Repository name (string, required) + - `name`: 标签名称。(string, required) + - `owner`: 仓库所有者（用户名或组织名）(string, required) + - `repo`: 仓库名称 (string, required) -- **label_write** - Write operations on repository labels +- **label_write** - 对仓库标签执行写入操作 - **Required OAuth Scopes**: `repo` - - `color`: Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'. (string, optional) - - `description`: Label description text. Optional for 'create' and 'update'. (string, optional) - - `method`: Operation to perform: 'create', 'update', or 'delete' (string, required) - - `name`: Label name - required for all operations (string, required) - - `new_name`: New name for the label (used only with 'update' method to rename) (string, optional) - - `owner`: Repository owner (username or organization name) (string, required) - - `repo`: Repository name (string, required) + - `color`: 标签颜色，为不带 '#' 前缀的 6 位十六进制代码（例如 'f29513'）。'create' 时必填，'update' 时可选。(string, optional) + - `description`: 标签描述文本。'create' 和 'update' 时可选。(string, optional) + - `method`: 要执行的操作：'create'、'update' 或 'delete' (string, required) + - `name`: 标签名称 - 所有操作均必填 (string, required) + - `new_name`: 标签的新名称（仅在与 'update' 方法一起使用时用于重命名）(string, optional) + - `owner`: 仓库所有者（用户名或组织名）(string, required) + - `repo`: 仓库名称 (string, required) -- **list_label** - List labels from a repository +- **list_label** - 列出仓库中的标签 - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (username or organization name) - required for all operations (string, required) - - `repo`: Repository name - required for all operations (string, required) + - `owner`: 仓库所有者（用户名或组织名）- 所有操作均必填 (string, required) + - `repo`: 仓库名称 - 所有操作均必填 (string, required)
-bell Notifications +bell 通知（Notifications） -- **dismiss_notification** - Dismiss notification - - **Required OAuth Scopes**: `notifications` - - `state`: The new state of the notification (read/done) (string, required) - - `threadID`: The ID of the notification thread (string, required) +- **dismiss_notification** - 关闭通知 + - **Required OAuth Scopes**：`notifications` + - `state`：通知的新状态（read/done）（string，必填） + - `threadID`：通知线程的 ID（string，必填） -- **get_notification_details** - Get notification details - - **Required OAuth Scopes**: `notifications` - - `notificationID`: The ID of the notification (string, required) +- **get_notification_details** - 获取通知详情 + - **Required OAuth Scopes**：`notifications` + - `notificationID`：通知的 ID（string，必填） -- **list_notifications** - List notifications - - **Required OAuth Scopes**: `notifications` - - `before`: Only show notifications updated before the given time (ISO 8601 format) (string, optional) - - `filter`: Filter notifications to, use default unless specified. Read notifications are ones that have already been acknowledged by the user. Participating notifications are those that the user is directly involved in, such as issues or pull requests they have commented on or created. (string, optional) - - `owner`: Optional repository owner. If provided with repo, only notifications for this repository are listed. (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Optional repository name. If provided with owner, only notifications for this repository are listed. (string, optional) - - `since`: Only show notifications updated after the given time (ISO 8601 format) (string, optional) +- **list_notifications** - 列出通知 + - **Required OAuth Scopes**：`notifications` + - `before`：仅显示在指定时间之前更新的通知（ISO 8601 格式）（string，可选） + - `filter`：过滤通知的范围，除非另有指定否则使用默认值。已读（Read）通知是指用户已确认的通知。参与（Participating）通知是指用户直接相关的通知，例如用户评论或创建的 issue 或 pull request。（string，可选） + - `owner`：可选的仓库所有者。若与 repo 一起提供，则仅列出该仓库的通知。（string，可选） + - `page`：分页页码（最小为 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：可选的仓库名称。若与 owner 一起提供，则仅列出该仓库的通知。（string，可选） + - `since`：仅显示在指定时间之后更新的通知（ISO 8601 格式）（string，可选） -- **manage_notification_subscription** - Manage notification subscription - - **Required OAuth Scopes**: `notifications` - - `action`: Action to perform: ignore, watch, or delete the notification subscription. (string, required) - - `notificationID`: The ID of the notification thread. (string, required) +- **manage_notification_subscription** - 管理通知订阅 + - **Required OAuth Scopes**：`notifications` + - `action`：要执行的操作：ignore（忽略）、watch（关注）或 delete（删除）该通知订阅。（string，必填） + - `notificationID`：通知线程的 ID。（string，必填） -- **manage_repository_notification_subscription** - Manage repository notification subscription - - **Required OAuth Scopes**: `notifications` - - `action`: Action to perform: ignore, watch, or delete the repository notification subscription. (string, required) - - `owner`: The account owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) +- **manage_repository_notification_subscription** - 管理仓库通知订阅 + - **Required OAuth Scopes**：`notifications` + - `action`：要执行的操作：ignore（忽略）、watch（关注）或 delete（删除）该仓库通知订阅。（string，必填） + - `owner`：仓库所属账户的所有者。（string，必填） + - `repo`：仓库名称。（string，必填） -- **mark_all_notifications_read** - Mark all notifications as read - - **Required OAuth Scopes**: `notifications` - - `lastReadAt`: Describes the last point that notifications were checked (optional). Default: Now (string, optional) - - `owner`: Optional repository owner. If provided with repo, only notifications for this repository are marked as read. (string, optional) - - `repo`: Optional repository name. If provided with owner, only notifications for this repository are marked as read. (string, optional) +- **mark_all_notifications_read** - 将所有通知标记为已读 + - **Required OAuth Scopes**：`notifications` + - `lastReadAt`：描述上次检查通知的时间点（可选）。默认值：Now（string，可选） + - `owner`：可选的仓库所有者。若与 repo 一起提供，则仅将该仓库的通知标记为已读。（string，可选） + - `repo`：可选的仓库名称。若与 owner 一起提供，则仅将该仓库的通知标记为已读。（string，可选）
-organization Organizations +organization 组织（Organizations） -- **search_orgs** - Search organizations - - **Required OAuth Scopes**: `read:org` - - **Accepted OAuth Scopes**: `admin:org`, `read:org`, `write:org` - - `order`: Sort order (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Organization search query. Examples: 'microsoft', 'location:california', 'created:>=2025-01-01'. Search is automatically scoped to type:org. (string, required) - - `sort`: Sort field by category (string, optional) +- **search_orgs** - 搜索组织 + - **Required OAuth Scopes**：`read:org` + - **Accepted OAuth Scopes**：`admin:org`、`read:org`、`write:org` + - `order`：排序顺序（string，可选） + - `page`：分页页码（最小为 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `query`：组织搜索查询。示例：'microsoft'、'location:california'、'created:>=2025-01-01'。搜索会自动限定为 type:org。（string，必填） + - `sort`：按类别排序的字段（string，可选）
-project Projects +project 项目（Projects） -- **projects_get** - Get details of GitHub Projects resources - - **Required OAuth Scopes**: `read:project` - - **Accepted OAuth Scopes**: `project`, `read:project` - - `field_id`: The field's ID. Required for 'get_project_field' method. (number, optional) - - `field_names`: Specific list of field names to include in the response when getting a project item (e.g. ["Status", "Priority"]). Resolved server-side to field IDs — pass this instead of 'fields' when you only know the human-readable names. Mutually exclusive with 'fields' — provide one, not both. Only used for 'get_project_item' method. (string[], optional) - - `fields`: Specific list of field IDs to include in the response when getting a project item (e.g. ["102589", "985201", "169875"]). If neither 'fields' nor 'field_names' is provided, only the title field is included. Mutually exclusive with 'field_names' — provide one, not both. Only used for 'get_project_item' method. (string[], optional) - - `item_id`: The item's ID. Required for 'get_project_item' method. (number, optional) - - `method`: The method to execute (string, required) - - `owner`: The owner (user or organization login). The name is not case sensitive. (string, optional) - - `owner_type`: Owner type (user or org). If not provided, will be automatically detected. (string, optional) - - `project_number`: The project's number. (number, optional) - - `status_update_id`: The node ID of the project status update. Required for 'get_project_status_update' method. (string, optional) +- **projects_get** - 获取 GitHub Projects 资源详情 + - **Required OAuth Scopes**：`read:project` + - **Accepted OAuth Scopes**：`project`、`read:project` + - `field_id`：字段的 ID。'get_project_field' 方法必填。（number，可选） + - `field_names`：获取项目条目时要包含在响应中的字段名称列表（例如 ["Status", "Priority"]）。由服务端解析为字段 ID——当你只知道人类可读名称时，请传此参数而非 'fields'。与 'fields' 互斥——二者只提供其一。仅用于 'get_project_item' 方法。（string[]，可选） + - `fields`：获取项目条目时要包含在响应中的字段 ID 列表（例如 ["102589", "985201", "169875"]）。若既未提供 'fields' 也未提供 'field_names'，则仅包含标题字段。与 'field_names' 互斥——二者只提供其一。仅用于 'get_project_item' 方法。（string[]，可选） + - `item_id`：条目的 ID。'get_project_item' 方法必填。（number，可选） + - `method`：要执行的方法（string，必填） + - `owner`：所有者（用户或组织登录名）。名称不区分大小写。（string，可选） + - `owner_type`：所有者类型（user 或 org）。若未提供，将自动检测。（string，可选） + - `project_number`：项目编号。（number，可选） + - `status_update_id`：项目状态更新的 node ID。'get_project_status_update' 方法必填。（string，可选） -- **projects_list** - List GitHub Projects resources - - **Required OAuth Scopes**: `read:project` - - **Accepted OAuth Scopes**: `project`, `read:project` - - `after`: Forward pagination cursor from previous pageInfo.nextCursor. (string, optional) - - `before`: Backward pagination cursor from previous pageInfo.prevCursor (rare). (string, optional) - - `field_names`: Field names to include when listing project items (e.g. ["Status", "Priority"]). Resolved server-side to field IDs — pass this instead of 'fields' when you only know the human-readable names. Names that fail to resolve return a structured error. Mutually exclusive with 'fields' — provide one, not both. Only used for 'list_project_items' method. (string[], optional) - - `fields`: Field IDs to include when listing project items (e.g. ["102589", "985201"]). CRITICAL: Always provide to get field values. Without this (and without 'field_names'), only titles returned. Mutually exclusive with 'field_names' — provide one, not both. Only used for 'list_project_items' method. (string[], optional) - - `method`: The action to perform (string, required) - - `owner`: The owner (user or organization login). The name is not case sensitive. (string, required) - - `owner_type`: Owner type (user or org). If not provided, will automatically try both. (string, optional) - - `per_page`: Results per page (max 50) (number, optional) - - `project_number`: The project's number. Required for 'list_project_fields', 'list_project_items', and 'list_project_status_updates' methods. (number, optional) - - `query`: Filter/query string. For list_projects: filter by title text and state (e.g. "roadmap is:open"). For list_project_items: advanced filtering using GitHub's project filtering syntax. (string, optional) +- **projects_list** - 列出 GitHub Projects 资源 + - **Required OAuth Scopes**：`read:project` + - **Accepted OAuth Scopes**：`project`、`read:project` + - `after`：来自上一页 pageInfo.nextCursor 的正向分页游标。（string，可选） + - `before`：来自上一页 pageInfo.prevCursor 的反向分页游标（较少使用）。（string，可选） + - `field_names`：列出项目条目时要包含的字段名称（例如 ["Status", "Priority"]）。由服务端解析为字段 ID——当你只知道人类可读名称时，请传此参数而非 'fields'。无法解析的名称会返回结构化错误。与 'fields' 互斥——二者只提供其一。仅用于 'list_project_items' 方法。（string[]，可选） + - `fields`：列出项目条目时要包含的字段 ID（例如 ["102589", "985201"]）。重要：务必提供以获取字段值。若不提供此项（且不提供 'field_names'），则仅返回标题。与 'field_names' 互斥——二者只提供其一。仅用于 'list_project_items' 方法。（string[]，可选） + - `method`：要执行的操作（string，必填） + - `owner`：所有者（用户或组织登录名）。名称不区分大小写。（string，必填） + - `owner_type`：所有者类型（user 或 org）。若未提供，将自动尝试两者。（string，可选） + - `per_page`：每页结果数（最大 50）（number，可选） + - `project_number`：项目编号。'list_project_fields'、'list_project_items' 和 'list_project_status_updates' 方法必填。（number，可选） + - `query`：过滤/查询字符串。对于 list_projects：按标题文本和状态过滤（例如 "roadmap is:open"）。对于 list_project_items：使用 GitHub 项目过滤语法进行高级过滤。（string，可选） -- **projects_write** - Manage GitHub Projects - - **Required OAuth Scopes**: `project` - - `body`: The body of the status update (markdown). Used for 'create_project_status_update' method. (string, optional) - - `field_name`: The name of the iteration field (e.g. 'Sprint'). Required for 'create_iteration_field' method. (string, optional) - - `issue_number`: The issue number. Required for 'add_project_item' when item_type is 'issue'. Also accepted by 'update_project_item' to resolve the item by issue number (combine with item_owner and item_repo). (number, optional) - - `item_id`: The project item ID. Required for 'delete_project_item'. For 'update_project_item', provide either item_id, or (item_owner + item_repo + issue_number) to resolve the item by issue. (number, optional) - - `item_owner`: The owner (user or organization) of the repository containing the issue or pull request. Required for 'add_project_item' method. Also accepted by 'update_project_item' when resolving the item by issue number. (string, optional) - - `item_repo`: The name of the repository containing the issue or pull request. Required for 'add_project_item' method. Also accepted by 'update_project_item' when resolving the item by issue number. (string, optional) - - `item_type`: The item's type, either issue or pull_request. Required for 'add_project_item' method. (string, optional) - - `iteration_duration`: Duration in days for iterations of the field (e.g. 7 for weekly, 14 for bi-weekly). Required for 'create_iteration_field' method. (number, optional) - - `iterations`: Custom iterations for 'create_iteration_field' method. Only set this when you need iterations with varying durations, breaks between them, or specific titles. Otherwise omit it: GitHub auto-creates three iterations of 'iteration_duration' days starting on 'start_date', which is the right choice for most cases. (object[], optional) - - `method`: The method to execute (string, required) - - `owner`: The project owner (user or organization login). The name is not case sensitive. (string, required) - - `owner_type`: Owner type (user or org). Required for 'create_project' method. If not provided for other methods, will be automatically detected. (string, optional) - - `project_number`: The project's number. Required for all methods except 'create_project'. (number, optional) - - `pull_request_number`: The pull request number (use when item_type is 'pull_request' for 'add_project_item' method). Provide either issue_number or pull_request_number. (number, optional) - - `start_date`: Start date in YYYY-MM-DD format. Used for 'create_project_status_update' and 'create_iteration_field' methods. (string, optional) - - `status`: The status of the project. Used for 'create_project_status_update' method. (string, optional) - - `target_date`: The target date of the status update in YYYY-MM-DD format. Used for 'create_project_status_update' method. (string, optional) - - `title`: The project title. Required for 'create_project' method. (string, optional) - - `updated_field`: Object describing the field to update and its new value. Required for 'update_project_item'. Two shapes are accepted: (1) by ID — {"id": 123456, "value": "..."}; (2) by name — {"name": "Status", "value": "In Progress"}. For single-select fields, option-name resolution requires the by-name shape; on the by-ID shape, pass the option ID. Set value to null to clear the field. (object, optional) +- **projects_write** - 管理 GitHub Projects + - **Required OAuth Scopes**：`project` + - `body`：状态更新的正文（markdown）。用于 'create_project_status_update' 方法。（string，可选） + - `field_name`：迭代字段的名称（例如 'Sprint'）。'create_iteration_field' 方法必填。（string，可选） + - `issue_number`：issue 编号。当 item_type 为 'issue' 时，'add_project_item' 必填。'update_project_item' 也接受此参数，用于通过 issue 编号解析条目（需与 item_owner 和 item_repo 组合使用）。（number，可选） + - `item_id`：项目条目 ID。'delete_project_item' 必填。对于 'update_project_item'，请提供 item_id，或提供（item_owner + item_repo + issue_number）以通过 issue 解析条目。（number，可选） + - `item_owner`：包含该 issue 或 pull request 的仓库所有者（用户或组织）。'add_project_item' 方法必填。'update_project_item' 在通过 issue 编号解析条目时也接受此参数。（string，可选） + - `item_repo`：包含该 issue 或 pull request 的仓库名称。'add_project_item' 方法必填。'update_project_item' 在通过 issue 编号解析条目时也接受此参数。（string，可选） + - `item_type`：条目类型，为 issue 或 pull_request。'add_project_item' 方法必填。（string，可选） + - `iteration_duration`：该字段每次迭代的时长（天）（例如 7 表示每周，14 表示每两周）。'create_iteration_field' 方法必填。（number，可选） + - `iterations`：用于 'create_iteration_field' 方法的自定义迭代。仅在需要时长不等的迭代、迭代之间有间隔，或需要特定标题时设置。否则请省略：GitHub 会自动创建三个时长为 'iteration_duration' 天、从 'start_date' 开始的迭代，这对大多数场景都合适。（object[]，可选） + - `method`：要执行的方法（string，必填） + - `owner`：项目所有者（用户或组织登录名）。名称不区分大小写。（string，必填） + - `owner_type`：所有者类型（user 或 org）。'create_project' 方法必填。其他方法若未提供，将自动检测。（string，可选） + - `project_number`：项目编号。除 'create_project' 外的所有方法均必填。（number，可选） + - `pull_request_number`：pull request 编号（当 item_type 为 'pull_request' 时用于 'add_project_item' 方法）。请提供 issue_number 或 pull_request_number 之一。（number，可选） + - `start_date`：开始日期，格式为 YYYY-MM-DD。用于 'create_project_status_update' 和 'create_iteration_field' 方法。（string，可选） + - `status`：项目状态。用于 'create_project_status_update' 方法。（string，可选） + - `target_date`：状态更新的目标日期，格式为 YYYY-MM-DD。用于 'create_project_status_update' 方法。（string，可选） + - `title`：项目标题。'create_project' 方法必填。（string，可选） + - `updated_field`：描述要更新的字段及其新值的对象。'update_project_item' 必填。接受两种形态：（1）按 ID——{"id": 123456, "value": "..."}；（2）按名称——{"name": "Status", "value": "In Progress"}。对于单选字段，选项名称解析需要使用按名称的形态；在按 ID 的形态下，请传入选项 ID。将 value 设为 null 可清空该字段。（object，可选）
-git-pull-request Pull Requests +git-pull-request Pull Requests（拉取请求） -- **add_comment_to_pending_review** - Add review comment to the requester's latest pending pull request review - - **Required OAuth Scopes**: `repo` - - `body`: The text of the review comment (string, required) - - `line`: The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range (number, optional) - - `owner`: Repository owner (string, required) - - `path`: The relative path to the file that necessitates a comment (string, required) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) - - `side`: The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state (string, optional) - - `startLine`: For multi-line comments, the first line of the range that the comment applies to (number, optional) - - `startSide`: For multi-line comments, the starting side of the diff that the comment applies to. LEFT indicates the previous state, RIGHT indicates the new state (string, optional) - - `subjectType`: The level at which the comment is targeted (string, required) +- **add_comment_to_pending_review** - 向请求者最新的待处理拉取请求审查（pull request review）添加审查评论 + - **Required OAuth Scopes（必需的 OAuth 作用域）**: `repo` + - `body`: 审查评论的文本（string，必填） + - `line`: 审查评论所针对的拉取请求 diff 中 blob 的行号。对于多行评论，为范围的最后一条行号（number，可选） + - `owner`: 仓库所有者（string，必填） + - `path`: 需要添加评论的文件的相对路径（string，必填） + - `pullNumber`: 拉取请求编号（number，必填） + - `repo`: 仓库名称（string，必填） + - `side`: 要评论的 diff 侧。LEFT 表示先前状态，RIGHT 表示新状态（string，可选） + - `startLine`: 对于多行评论，评论所适用范围的第一条行号（number，可选） + - `startSide`: 对于多行评论，评论所适用 diff 的起始侧。LEFT 表示先前状态，RIGHT 表示新状态（string，可选） + - `subjectType`: 评论所针对的层级（string，必填） -- **add_reply_to_pull_request_comment** - Add reply to pull request comment +- **add_reply_to_pull_request_comment** - 为拉取请求评论添加回复 - **Required OAuth Scopes**: `repo` - - `body`: The text of the reply. Required unless reaction is provided. (string, optional) - - `commentId`: The numeric ID of the pull request review comment to reply or react to. Use the number from a #discussion_r... anchor, not the GraphQL thread node ID (PRRT_...). (number, required) - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number. Required when body is provided. (number, optional) - - `reaction`: Emoji reaction to add. Required unless body is provided. (string, optional) - - `repo`: Repository name (string, required) + - `body`: 回复文本。除非提供了 reaction，否则为必填项。（string，可选） + - `commentId`: 要回复或做出反应的拉取请求审查评论的数字 ID。请使用 #discussion_r... 锚点中的编号，而非 GraphQL 线程节点 ID（PRRT_...）。（number，必填） + - `owner`: 仓库所有者（string，必填） + - `pullNumber`: 拉取请求编号。提供 body 时为必填项。（number，可选） + - `reaction`: 要添加的表情符号反应（emoji reaction）。除非提供了 body，否则为必填项。（string，可选） + - `repo`: 仓库名称（string，必填） -- **create_pull_request** - Open new pull request +- **create_pull_request** - 打开新的拉取请求 - **Required OAuth Scopes**: `repo` - - `base`: Branch to merge into (string, required) - - `body`: PR description (string, optional) - - `draft`: Create as draft PR (boolean, optional) - - `head`: Branch containing changes (string, required) - - `maintainer_can_modify`: Allow maintainer edits (boolean, optional) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `reviewers`: GitHub usernames or ORG/team-slug team reviewers to request reviews from (string[], optional) - - `title`: PR title (string, required) + - `base`: 要合并到的分支（string，必填） + - `body`: PR 描述（string，可选） + - `draft`: 创建为草稿 PR（boolean，可选） + - `head`: 包含更改的分支（string，必填） + - `maintainer_can_modify`: 允许维护者编辑（boolean，可选） + - `owner`: 仓库所有者（string，必填） + - `repo`: 仓库名称（string，必填） + - `reviewers`: 要请求审查的 GitHub 用户名或 ORG/team-slug 团队审查者（string[]，可选） + - `title`: PR 标题（string，必填） -- **list_pull_requests** - List pull requests +- **list_pull_requests** - 列出拉取请求 - **Required OAuth Scopes**: `repo` - - `base`: Filter by base branch (string, optional) - - `direction`: Sort direction (string, optional) - - `head`: Filter by head user/org and branch (string, optional) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) - - `sort`: Sort by (string, optional) - - `state`: Filter by state (string, optional) + - `base`: 按基础分支筛选（string，可选） + - `direction`: 排序方向（string，可选） + - `head`: 按 head 用户/组织及分支筛选（string，可选） + - `owner`: 仓库所有者（string，必填） + - `page`: 分页页码（最小为 1）（number，可选） + - `perPage`: 分页每页结果数（最小为 1，最大为 100）（number，可选） + - `repo`: 仓库名称（string，必填） + - `sort`: 排序字段（string，可选） + - `state`: 按状态筛选（string，可选） -- **merge_pull_request** - Merge pull request +- **merge_pull_request** - 合并拉取请求 - **Required OAuth Scopes**: `repo` - - `commit_message`: Extra detail for merge commit (string, optional) - - `commit_title`: Title for merge commit (string, optional) - - `merge_method`: Merge method (string, optional) - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) + - `commit_message`: 合并提交的额外详情（string，可选） + - `commit_title`: 合并提交的标题（string，可选） + - `merge_method`: 合并方法（string，可选） + - `owner`: 仓库所有者（string，必填） + - `pullNumber`: 拉取请求编号（number，必填） + - `repo`: 仓库名称（string，必填） -- **pull_request_read** - Get details for a single pull request +- **pull_request_read** - 获取单个拉取请求的详情 - **Required OAuth Scopes**: `repo` - - `after`: Cursor for pagination, used only by the get_review_comments method. Pass the endCursor from the previous page's PageInfo to fetch the next page. (string, optional) - - `method`: Action to specify what pull request data needs to be retrieved from GitHub. - Possible options: - 1. get - Get details of a specific pull request. - 2. get_diff - Get the diff of a pull request. - 3. get_status - Get combined commit status of a head commit in a pull request. - 4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned. - 5. get_commits - Get the list of commits on a pull request. Use with pagination parameters to control the number of results returned. - 6. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results. - 7. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method. Use with pagination parameters to control the number of results returned. - 8. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned. - 9. get_check_runs - Get check runs for the head commit of a pull request. Check runs are the individual CI/CD jobs and checks that run on the PR. - (string, required) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) + - `after`: 分页游标，仅由 get_review_comments 方法使用。传入上一页 PageInfo 的 endCursor 以获取下一页。（string，可选） + - `method`: 指定需要从 GitHub 获取哪些拉取请求数据的操作。 + 可选选项： + 1. get - 获取特定拉取请求的详情。 + 2. get_diff - 获取拉取请求的 diff。 + 3. get_status - 获取拉取请求中 head 提交的组合提交状态。 + 4. get_files - 获取拉取请求中变更的文件列表。可配合分页参数控制返回结果数量。 + 5. get_commits - 获取拉取请求上的提交列表。可配合分页参数控制返回结果数量。 + 6. get_review_comments - 获取拉取请求上的审查线程。每个线程包含在拉取请求审查期间于同一代码位置做出的逻辑分组审查评论。返回带有元数据（isResolved、isOutdated、isCollapsed）的线程及其关联评论。使用基于游标的分页（perPage、after）控制结果。 + 7. get_reviews - 获取拉取请求上的审查。当被要求提供审查评论时，请使用 get_review_comments 方法。可配合分页参数控制返回结果数量。 + 8. get_comments - 获取拉取请求上的评论。若用户未明确要求审查评论，请使用此方法。可配合分页参数控制返回结果数量。 + 9. get_check_runs - 获取拉取请求 head 提交的检查运行（check runs）。检查运行是在 PR 上运行的各个 CI/CD 作业和检查。 + （string，必填） + - `owner`: 仓库所有者（string，必填） + - `page`: 分页页码（最小为 1）（number，可选） + - `perPage`: 分页每页结果数（最小为 1，最大为 100）（number，可选） + - `pullNumber`: 拉取请求编号（number，必填） + - `repo`: 仓库名称（string，必填） -- **pull_request_review_write** - Write operations (create, submit, delete) on pull request reviews +- **pull_request_review_write** - 对拉取请求审查执行写入操作（创建、提交、删除） - **Required OAuth Scopes**: `repo` - - `body`: Review comment text (string, optional) - - `commitID`: SHA of commit to review (string, optional) - - `event`: Review action to perform. (string, optional) - - `method`: The write operation to perform on pull request review. (string, required) - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) - - `threadId`: The node ID of the review thread (e.g., PRRT_kwDOxxx). Required for resolve_thread and unresolve_thread methods. Get thread IDs from pull_request_read with method get_review_comments. (string, optional) + - `body`: 审查评论文本（string，可选） + - `commitID`: 要审查的提交的 SHA（string，可选） + - `event`: 要执行的审查操作。（string，可选） + - `method`: 要对拉取请求审查执行的写入操作。（string，必填） + - `owner`: 仓库所有者（string，必填） + - `pullNumber`: 拉取请求编号（number，必填） + - `repo`: 仓库名称（string，必填） + - `threadId`: 审查线程的节点 ID（例如 PRRT_kwDOxxx）。resolve_thread 和 unresolve_thread 方法需要此参数。可通过 pull_request_read 的 get_review_comments 方法获取线程 ID。（string，可选） -- **search_pull_requests** - Search pull requests +- **search_pull_requests** - 搜索拉取请求 - **Required OAuth Scopes**: `repo` - - `order`: Sort order (string, optional) - - `owner`: Optional repository owner. If provided with repo, only pull requests for this repository are listed. (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Search query using GitHub pull request search syntax (string, required) - - `repo`: Optional repository name. If provided with owner, only pull requests for this repository are listed. (string, optional) - - `sort`: Sort field by number of matches of categories, defaults to best match (string, optional) + - `order`: 排序顺序（string，可选） + - `owner`: 可选的仓库所有者。若与 repo 一并提供，则仅列出该仓库的拉取请求。（string，可选） + - `page`: 分页页码（最小为 1）（number，可选） + - `perPage`: 分页每页结果数（最小为 1，最大为 100）（number，可选） + - `query`: 使用 GitHub 拉取请求搜索语法的搜索查询（string，必填） + - `repo`: 可选的仓库名称。若与 owner 一并提供，则仅列出该仓库的拉取请求。（string，可选） + - `sort`: 按各类别匹配数量排序的字段，默认为最佳匹配（string，可选） -- **update_pull_request** - Edit pull request +- **update_pull_request** - 编辑拉取请求 - **Required OAuth Scopes**: `repo` - - `base`: New base branch name (string, optional) - - `body`: New description (string, optional) - - `draft`: Mark pull request as draft (true) or ready for review (false) (boolean, optional) - - `maintainer_can_modify`: Allow maintainer edits (boolean, optional) - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number to update (number, required) - - `repo`: Repository name (string, required) - - `reviewers`: GitHub usernames or ORG/team-slug team reviewers to request reviews from (string[], optional) - - `state`: New state (string, optional) - - `title`: New title (string, optional) + - `base`: 新的基础分支名称（string，可选） + - `body`: 新描述（string，可选） + - `draft`: 将拉取请求标记为草稿（true）或准备审查（false）（boolean，可选） + - `maintainer_can_modify`: 允许维护者编辑（boolean，可选） + - `owner`: 仓库所有者（string，必填） + - `pullNumber`: 要更新的拉取请求编号（number，必填） + - `repo`: 仓库名称（string，必填） + - `reviewers`: 要请求审查的 GitHub 用户名或 ORG/team-slug 团队审查者（string[]，可选） + - `state`: 新状态（string，可选） + - `title`: 新标题（string，可选） -- **update_pull_request_branch** - Update pull request branch - - **Required OAuth Scopes**: `repo` - - `expectedHeadSha`: The expected SHA of the pull request's HEAD ref (string, optional) - - `owner`: Repository owner (string, required) - - `pullNumber`: Pull request number (number, required) - - `repo`: Repository name (string, required) +- **update_pull_request_branch** - 更新 Pull Request 分支 + - **所需 OAuth 权限范围**：`repo` + - `expectedHeadSha`：拉取请求 HEAD 引用的预期 SHA（string，可选） + - `owner`：仓库所有者（string，必填） + - `pullNumber`：拉取请求编号（number，必填） + - `repo`：仓库名称（string，必填）
@@ -1243,273 +1248,273 @@ The following sets of tools are available: repo Repositories -- **create_branch** - Create branch - - **Required OAuth Scopes**: `repo` - - `branch`: Name for new branch (string, required) - - `from_branch`: Source branch (defaults to repo default) (string, optional) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **create_branch** - 创建分支 + - **所需 OAuth 权限范围**：`repo` + - `branch`：新分支名称（string，必填） + - `from_branch`：源分支（默认为仓库默认分支）（string，可选） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **create_or_update_file** - Create or update file - - **Required OAuth Scopes**: `repo` - - `branch`: Branch to create/update the file in (string, required) - - `content`: Content of the file (string, required) - - `message`: Commit message (string, required) - - `owner`: Repository owner (username or organization) (string, required) - - `path`: Path where to create/update the file (string, required) - - `repo`: Repository name (string, required) - - `sha`: The blob SHA of the file being replaced. Required if the file already exists. (string, optional) +- **create_or_update_file** - 创建或更新文件 + - **所需 OAuth 权限范围**：`repo` + - `branch`：创建/更新文件所在的分支（string，必填） + - `content`：文件内容（string，必填） + - `message`：提交消息（string，必填） + - `owner`：仓库所有者（用户名或组织）（string，必填） + - `path`：创建/更新文件的路径（string，必填） + - `repo`：仓库名称（string，必填） + - `sha`：被替换文件的 blob SHA。若文件已存在则为必填。（string，可选） -- **create_repository** - Create repository - - **Required OAuth Scopes**: `repo` - - `autoInit`: Initialize with README (boolean, optional) - - `description`: Repository description (string, optional) - - `name`: Repository name (string, required) - - `organization`: Organization to create the repository in (omit to create in your personal account) (string, optional) - - `private`: Whether the repository should be private. Defaults to true (private) when omitted. (boolean, optional) +- **create_repository** - 创建仓库 + - **所需 OAuth 权限范围**：`repo` + - `autoInit`：是否使用 README 初始化（boolean，可选） + - `description`：仓库描述（string，可选） + - `name`：仓库名称（string，必填） + - `organization`：创建仓库的组织（省略则在个人账号下创建）（string，可选） + - `private`：仓库是否应为私有。省略时默认为 true（私有）。（boolean，可选） -- **delete_file** - Delete file - - **Required OAuth Scopes**: `repo` - - `branch`: Branch to delete the file from (string, required) - - `message`: Commit message (string, required) - - `owner`: Repository owner (username or organization) (string, required) - - `path`: Path to the file to delete (string, required) - - `repo`: Repository name (string, required) +- **delete_file** - 删除文件 + - **所需 OAuth 权限范围**：`repo` + - `branch`：删除文件所在的分支（string，必填） + - `message`：提交消息（string，必填） + - `owner`：仓库所有者（用户名或组织）（string，必填） + - `path`：要删除的文件路径（string，必填） + - `repo`：仓库名称（string，必填） -- **fork_repository** - Fork repository - - **Required OAuth Scopes**: `repo` - - `organization`: Organization to fork to (string, optional) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **fork_repository** - Fork 仓库 + - **所需 OAuth 权限范围**：`repo` + - `organization`：Fork 到的组织（string，可选） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **get_commit** - Get commit details - - **Required OAuth Scopes**: `repo` - - `detail`: Level of detail to include for changed files. "none" omits stats and files entirely. "stats" (default) includes per-file metadata: filename, status, and lines-of-code counts (additions, deletions, changes), with no patch content. "full_patch" additionally includes the unified diff content for each file and can be very large. (string, optional) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) - - `sha`: Commit SHA, branch name, or tag name (string, required) +- **get_commit** - 获取提交详情 + - **所需 OAuth 权限范围**：`repo` + - `detail`：变更文件的详细程度。"none" 会完全省略统计信息和文件。"stats"（默认）包含每个文件的元数据：文件名、状态以及代码行数统计（新增、删除、变更），不包含 patch 内容。"full_patch" 还会包含每个文件的统一 diff 内容，体积可能非常大。（string，可选） + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） + - `sha`：提交 SHA、分支名或标签名（string，必填） -- **get_file_contents** - Get file or directory contents - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (username or organization) (string, required) - - `path`: Path to file/directory (string, optional) - - `ref`: Accepts optional git refs such as `refs/tags/{tag}`, `refs/heads/{branch}` or `refs/pull/{pr_number}/head` (string, optional) - - `repo`: Repository name (string, required) - - `sha`: Accepts optional commit SHA. If specified, it will be used instead of ref (string, optional) +- **get_file_contents** - 获取文件或目录内容 + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（用户名或组织）（string，必填） + - `path`：文件/目录路径（string，可选） + - `ref`：接受可选的 git 引用，例如 `refs/tags/{tag}`、`refs/heads/{branch}` 或 `refs/pull/{pr_number}/head`（string，可选） + - `repo`：仓库名称（string，必填） + - `sha`：接受可选的提交 SHA。若指定，将替代 ref 使用（string，可选） -- **get_latest_release** - Get latest release - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **get_latest_release** - 获取最新 Release + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **get_release_by_tag** - Get a release by tag name - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `tag`: Tag name (e.g., 'v1.0.0') (string, required) +- **get_release_by_tag** - 按标签名获取 Release + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） + - `tag`：标签名（例如 'v1.0.0'）（string，必填） -- **get_tag** - Get tag details - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) - - `tag`: Tag name (string, required) +- **get_tag** - 获取标签详情 + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） + - `tag`：标签名（string，必填） -- **list_branches** - List branches - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) +- **list_branches** - 列出分支 + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） -- **list_commits** - List commits - - **Required OAuth Scopes**: `repo` - - `author`: Author username or email address to filter commits by (string, optional) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `path`: Only commits containing this file path will be returned (string, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) - - `sha`: Commit SHA, branch or tag name to list commits of. If not provided, uses the default branch of the repository. If a commit SHA is provided, will list commits up to that SHA. (string, optional) - - `since`: Only commits after this date will be returned (ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DD) (string, optional) - - `until`: Only commits before this date will be returned (ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DD) (string, optional) +- **list_commits** - 列出提交 + - **所需 OAuth 权限范围**：`repo` + - `author`：按作者用户名或电子邮件地址筛选提交（string，可选） + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `path`：仅返回包含此文件路径的提交（string，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） + - `sha`：要列出提交的提交 SHA、分支或标签名。若未提供，则使用仓库的默认分支。若提供提交 SHA，将列出截至该 SHA 的提交。（string，可选） + - `since`：仅返回此日期之后的提交（ISO 8601 格式：YYYY-MM-DDTHH:MM:SSZ 或 YYYY-MM-DD）（string，可选） + - `until`：仅返回此日期之前的提交（ISO 8601 格式：YYYY-MM-DDTHH:MM:SSZ 或 YYYY-MM-DD）（string，可选） -- **list_releases** - List releases - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) +- **list_releases** - 列出 Release + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） -- **list_repository_collaborators** - List repository collaborators - - **Required OAuth Scopes**: `repo` - - `affiliation`: Filter by affiliation. Can be one of: 'outside' (outside collaborators), 'direct' (all with permissions regardless of org membership), 'all' (all collaborators). Default: 'all' (string, optional) - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (default 1, min 1) (number, optional) - - `perPage`: Results per page for pagination (default 30, min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) +- **list_repository_collaborators** - 列出仓库协作者 + - **所需 OAuth 权限范围**：`repo` + - `affiliation`：按关联关系筛选。可选值：'outside'（外部协作者）、'direct'（所有具有权限的用户，不论是否为组织成员）、'all'（所有协作者）。默认值：'all'（string，可选） + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（默认 1，最小 1）（number，可选） + - `perPage`：每页结果数（默认 30，最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） -- **list_tags** - List tags - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: Repository name (string, required) +- **list_tags** - 列出标签 + - **所需 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `repo`：仓库名称（string，必填） -- **push_files** - Push files to repository - - **Required OAuth Scopes**: `repo` - - `branch`: Branch to push to (string, required) - - `files`: Array of file objects to push, each object with path (string) and content (string) (object[], required) - - `message`: Commit message (string, required) - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **push_files** - 推送文件到仓库 + - **所需 OAuth 权限范围**：`repo` + - `branch`：推送目标分支（string，必填） + - `files`：要推送的文件对象数组，每个对象包含 path（string）和 content（string）（object[]，必填） + - `message`：提交消息（string，必填） + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **search_code** - Search code - - **Required OAuth Scopes**: `repo` - - `order`: Sort order for results (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Search query (GitHub code search REST). Implicit AND between terms; supports `OR`, `NOT`, and `"quoted phrase"` for exact match. Qualifiers: `repo:owner/repo`, `org:`, `user:`, `language:`, `path:dir` (prefix match), `filename:exact.ext`, `extension:`, `in:file`, `in:path`, `size:`, `is:archived`, `is:fork`. Max 256 chars. Examples: `WithContext language:go org:github`; `"package main" repo:o/r`; `func extension:go path:cmd repo:o/r`; `NOT TODO language:go repo:o/r`. (string, required) - - `sort`: Sort field ('indexed' only) (string, optional) +- **search_code** - 搜索代码 + - **所需 OAuth 权限范围**：`repo` + - `order`：结果排序顺序（string，可选） + - `page`：分页页码（最小 1）（number，可选） + - `perPage`：每页结果数（最小 1，最大 100）（number，可选） + - `query`：搜索查询（GitHub 代码搜索 REST）。词条之间隐式 AND；支持 `OR`、`NOT` 和 `"quoted phrase"` 进行精确匹配。限定符：`repo:owner/repo`、`org:`、`user:`、`language:`、`path:dir`（前缀匹配）、`filename:exact.ext`、`extension:`、`in:file`、`in:path`、`size:`、`is:archived`、`is:fork`。最多 256 个字符。示例：`WithContext language:go org:github`；`"package main" repo:o/r`；`func extension:go path:cmd repo:o/r`；`NOT TODO language:go repo:o/r`。（string，必填） + - `sort`：排序字段（仅 'indexed'）（string，可选） -- **search_commits** - Search commits - - **Required OAuth Scopes**: `repo` - - `order`: Sort order (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Commit search query (GitHub commit search REST). Searches commit messages on the default branch only. Scope the search with `repo:owner/repo`, `org:`, or `user:` (queries without a scope qualifier match across all of GitHub and are usually not what you want). Other qualifiers: `author:`, `committer:`, `author-name:`, `committer-name:`, `author-email:`, `committer-email:`, `author-date:`, `committer-date:` (supports `>`, `<`, `>=`, `<=`, and `YYYY-MM-DD..YYYY-MM-DD` ranges), `merge:true|false`, `hash:`, `tree:`, `parent:`, `is:public`. Examples: `repo:owner/repo fix panic`; `org:github author:defunkt committer-date:>=2024-01-01`; `"refactor cache" repo:o/r`; `hash:abc1234 repo:o/r`. (string, required) - - `sort`: Sort by author or committer date (defaults to best match) (string, optional) +- **search_commits** - 搜索提交 + - **必需的 OAuth 权限范围**：`repo` + - `order`：排序顺序（string，可选） + - `page`：分页页码（最小值为 1）（number，可选） + - `perPage`：每页结果数（最小值为 1，最大值为 100）（number，可选） + - `query`：提交搜索查询（GitHub commit search REST）。仅在默认分支上搜索提交消息。请使用 `repo:owner/repo`、`org:` 或 `user:` 限定搜索范围（未带范围限定符的查询会在整个 GitHub 上匹配，通常并非你所需要的）。其他限定符：`author:`、`committer:`、`author-name:`、`committer-name:`、`author-email:`、`committer-email:`、`author-date:`、`committer-date:`（支持 `>`、`<`、`>=`、`<=` 和 `YYYY-MM-DD..YYYY-MM-DD` 范围）、`merge:true|false`、`hash:`、`tree:`、`parent:`、`is:public`。示例：`repo:owner/repo fix panic`；`org:github author:defunkt committer-date:>=2024-01-01`；`"refactor cache" repo:o/r`；`hash:abc1234 repo:o/r`。（string，必填） + - `sort`：按作者或提交者日期排序（默认为最佳匹配）（string，可选） -- **search_repositories** - Search repositories - - **Required OAuth Scopes**: `repo` - - `minimal_output`: Return minimal repository information (default: true). When false, returns full GitHub API repository objects. (boolean, optional) - - `order`: Sort order (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: Repository search query. Examples: 'machine learning in:name stars:>1000 language:python', 'topic:react', 'user:facebook'. Supports advanced search syntax for precise filtering. (string, required) - - `sort`: Sort repositories by field, defaults to best match (string, optional) +- **search_repositories** - 搜索仓库 + - **必需的 OAuth 权限范围**：`repo` + - `minimal_output`：返回精简的仓库信息（默认：true）。为 false 时返回完整的 GitHub API 仓库对象。（boolean，可选） + - `order`：排序顺序（string，可选） + - `page`：分页页码（最小值为 1）（number，可选） + - `perPage`：每页结果数（最小值为 1，最大值为 100）（number，可选） + - `query`：仓库搜索查询。示例：'machine learning in:name stars:>1000 language:python'、'topic:react'、'user:facebook'。支持高级搜索语法以实现精确筛选。（string，必填） + - `sort`：按字段对仓库排序，默认为最佳匹配（string，可选）
-shield-lock Secret Protection +shield-lock 密钥保护（Secret Protection） -- **get_secret_scanning_alert** - Get secret scanning alert - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `alertNumber`: The number of the alert. (number, required) - - `owner`: The owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) +- **get_secret_scanning_alert** - 获取密钥扫描告警 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `alertNumber`：告警编号。（number，必填） + - `owner`：仓库所有者。（string，必填） + - `repo`：仓库名称。（string，必填） -- **list_secret_scanning_alerts** - List secret scanning alerts - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `owner`: The owner of the repository. (string, required) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `repo`: The name of the repository. (string, required) - - `resolution`: Filter by resolution (string, optional) - - `secret_type`: A comma-separated list of secret types to return. All default secret patterns are returned. To return generic patterns, pass the token name(s) in the parameter. (string, optional) - - `state`: Filter by state (string, optional) +- **list_secret_scanning_alerts** - 列出密钥扫描告警 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `owner`：仓库所有者。（string，必填） + - `page`：分页页码（最小值为 1）（number，可选） + - `perPage`：每页结果数（最小值为 1，最大值为 100）（number，可选） + - `repo`：仓库名称。（string，必填） + - `resolution`：按处理方式筛选（string，可选） + - `secret_type`：以逗号分隔的密钥类型列表。默认返回所有默认密钥模式。要返回通用模式，请在参数中传入令牌名称。（string，可选） + - `state`：按状态筛选（string，可选）
-shield Security Advisories +shield 安全公告（Security Advisories） -- **get_global_security_advisory** - Get a global security advisory - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `ghsaId`: GitHub Security Advisory ID (format: GHSA-xxxx-xxxx-xxxx). (string, required) +- **get_global_security_advisory** - 获取全局安全公告 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `ghsaId`：GitHub 安全公告 ID（格式：GHSA-xxxx-xxxx-xxxx）。（string，必填） -- **list_global_security_advisories** - List global security advisories - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `affects`: Filter advisories by affected package or version (e.g. "package1,package2@1.0.0"). (string, optional) - - `cveId`: Filter by CVE ID. (string, optional) - - `cwes`: Filter by Common Weakness Enumeration IDs (e.g. ["79", "284", "22"]). (string[], optional) - - `ecosystem`: Filter by package ecosystem. (string, optional) - - `ghsaId`: Filter by GitHub Security Advisory ID (format: GHSA-xxxx-xxxx-xxxx). (string, optional) - - `isWithdrawn`: Whether to only return withdrawn advisories. (boolean, optional) - - `modified`: Filter by publish or update date or date range (ISO 8601 date or range). (string, optional) - - `published`: Filter by publish date or date range (ISO 8601 date or range). (string, optional) - - `severity`: Filter by severity. (string, optional) - - `type`: Advisory type. (string, optional) - - `updated`: Filter by update date or date range (ISO 8601 date or range). (string, optional) +- **list_global_security_advisories** - 列出全局安全公告 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `affects`：按受影响的包或版本筛选公告（例如 "package1,package2@1.0.0"）。（string，可选） + - `cveId`：按 CVE ID 筛选。（string，可选） + - `cwes`：按通用弱点枚举（Common Weakness Enumeration，CWE）ID 筛选（例如 ["79", "284", "22"]）。（string[]，可选） + - `ecosystem`：按包生态系统筛选。（string，可选） + - `ghsaId`：按 GitHub 安全公告 ID 筛选（格式：GHSA-xxxx-xxxx-xxxx）。（string，可选） + - `isWithdrawn`：是否仅返回已撤回的公告。（boolean，可选） + - `modified`：按发布或更新日期或日期范围筛选（ISO 8601 日期或范围）。（string，可选） + - `published`：按发布日期或日期范围筛选（ISO 8601 日期或范围）。（string，可选） + - `severity`：按严重程度筛选。（string，可选） + - `type`：公告类型。（string，可选） + - `updated`：按更新日期或日期范围筛选（ISO 8601 日期或范围）。（string，可选） -- **list_org_repository_security_advisories** - List org repository security advisories - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `direction`: Sort direction. (string, optional) - - `org`: The organization login. (string, required) - - `sort`: Sort field. (string, optional) - - `state`: Filter by advisory state. (string, optional) +- **list_org_repository_security_advisories** - 列出组织仓库安全公告 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `direction`：排序方向。（string，可选） + - `org`：组织登录名。（string，必填） + - `sort`：排序字段。（string，可选） + - `state`：按公告状态筛选。（string，可选） -- **list_repository_security_advisories** - List repository security advisories - - **Required OAuth Scopes**: `security_events` - - **Accepted OAuth Scopes**: `repo`, `security_events` - - `direction`: Sort direction. (string, optional) - - `owner`: The owner of the repository. (string, required) - - `repo`: The name of the repository. (string, required) - - `sort`: Sort field. (string, optional) - - `state`: Filter by advisory state. (string, optional) +- **list_repository_security_advisories** - 列出仓库安全公告 + - **必需的 OAuth 权限范围**：`security_events` + - **可接受的 OAuth 权限范围**：`repo`、`security_events` + - `direction`：排序方向。（string，可选） + - `owner`：仓库所有者。（string，必填） + - `repo`：仓库名称。（string，必填） + - `sort`：排序字段。（string，可选） + - `state`：按公告状态筛选。（string，可选）
-star Stargazers +star Star 用户（Stargazers） -- **list_starred_repositories** - List starred repositories - - **Required OAuth Scopes**: `repo` - - `direction`: The direction to sort the results by. (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `sort`: How to sort the results. Can be either 'created' (when the repository was starred) or 'updated' (when the repository was last pushed to). (string, optional) - - `username`: Username to list starred repositories for. Defaults to the authenticated user. (string, optional) +- **list_starred_repositories** - 列出已加星的仓库 + - **必需的 OAuth 权限范围**：`repo` + - `direction`：结果排序方向。（string，可选） + - `page`：分页页码（最小值为 1）（number，可选） + - `perPage`：每页结果数（最小值为 1，最大值为 100）（number，可选） + - `sort`：结果的排序方式。可以是 'created'（仓库被加星的时间）或 'updated'（仓库最后一次推送的时间）。（string，可选） + - `username`：要列出其已加星仓库的用户名。默认为已认证用户。（string，可选） -- **star_repository** - Star repository - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **star_repository** - 为仓库加星 + - **必需的 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填） -- **unstar_repository** - Unstar repository - - **Required OAuth Scopes**: `repo` - - `owner`: Repository owner (string, required) - - `repo`: Repository name (string, required) +- **unstar_repository** - 取消为仓库加星 + - **必需的 OAuth 权限范围**：`repo` + - `owner`：仓库所有者（string，必填） + - `repo`：仓库名称（string，必填）
-people Users +people 用户（Users） -- **search_users** - Search users - - **Required OAuth Scopes**: `repo` - - `order`: Sort order (string, optional) - - `page`: Page number for pagination (min 1) (number, optional) - - `perPage`: Results per page for pagination (min 1, max 100) (number, optional) - - `query`: User search query. Examples: 'john smith', 'location:seattle', 'followers:>100'. Search is automatically scoped to type:user. (string, required) - - `sort`: Sort users by number of followers or repositories, or when the person joined GitHub. (string, optional) +- **search_users** - 搜索用户 + - **必需的 OAuth 权限范围**：`repo` + - `order`：排序顺序（string，可选） + - `page`：分页页码（最小值为 1）（number，可选） + - `perPage`：每页结果数（最小值为 1，最大值为 100）（number，可选） + - `query`：用户搜索查询。示例：'john smith'、'location:seattle'、'followers:>100'。搜索会自动限定为 type:user。（string，必填） + - `sort`：按关注者数量、仓库数量或用户加入 GitHub 的时间排序。（string，可选）
-### Additional Tools in Remote GitHub MCP Server +### 远程 GitHub MCP Server 中的其他工具
Copilot -- **create_pull_request_with_copilot** - Perform task with GitHub Copilot coding agent - - `owner`: Repository owner. You can guess the owner, but confirm it with the user before proceeding. (string, required) - - `repo`: Repository name. You can guess the repository name, but confirm it with the user before proceeding. (string, required) - - `problem_statement`: Detailed description of the task to be performed (e.g., 'Implement a feature that does X', 'Fix bug Y', etc.) (string, required) - - `title`: Title for the pull request that will be created (string, required) - - `base_ref`: Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository's default branch (string, optional) +- **create_pull_request_with_copilot** - 使用 GitHub Copilot 编码代理执行任务 + - `owner`: 仓库所有者。你可以推测所有者，但在继续之前须与用户确认。（string，必填） + - `repo`: 仓库名称。你可以推测仓库名称，但在继续之前须与用户确认。（string，必填） + - `problem_statement`: 待执行任务的详细描述（例如「实现某项功能 X」「修复 bug Y」等）（string，必填） + - `title`: 将创建的拉取请求标题（string，必填） + - `base_ref`: 代理开始工作时使用的 Git 引用（例如分支）。若未指定，则默认为仓库的默认分支（string，可选）
@@ -1518,15 +1523,15 @@ The following sets of tools are available: Copilot Spaces - **Authentication note** - - Fine-grained PATs are not hidden by classic PAT scope filtering, so these tools may still appear even when the token cannot use them. - - For org-owned spaces, fine-grained PATs must be installed on the owning organization and include `organization_copilot_spaces: read`. - - If an org-owned space contains repository-backed resources, the token must also have access to every referenced repository or the space may be treated as not found. + - 细粒度 PAT（Personal Access Token）不会受经典 PAT 作用域过滤的隐藏，因此即使令牌无法使用这些工具，它们仍可能显示。 + - 对于组织拥有的 Space，细粒度 PAT 必须安装在所属组织上，并包含 `organization_copilot_spaces: read`。 + - 若组织拥有的 Space 包含以仓库为后端的资源，令牌还必须能访问所有被引用的仓库，否则该 Space 可能被视作不存在。 -- **get_copilot_space** - Get Copilot Space - - `owner`: The owner of the space. (string, required) - - `name`: The name of the space. (string, required) +- **get_copilot_space** - 获取 Copilot Space + - `owner`: Space 的所有者。（string，必填） + - `name`: Space 的名称。（string，必填） -- **list_copilot_spaces** - List Copilot Spaces +- **list_copilot_spaces** - 列出 Copilot Spaces @@ -1534,20 +1539,20 @@ The following sets of tools are available: GitHub Support Docs Search -- **github_support_docs_search** - Retrieve documentation relevant to answer GitHub product and support questions. Support topics include: GitHub Actions Workflows, Authentication, GitHub Support Inquiries, Pull Request Practices, Repository Maintenance, GitHub Pages, GitHub Packages, GitHub Discussions, Copilot Spaces - - `query`: Input from the user about the question they need answered. This is the latest raw unedited user message. You should ALWAYS leave the user message as it is, you should never modify it. (string, required) +- **github_support_docs_search** - 检索与回答 GitHub 产品和支持问题相关的文档。支持主题包括：GitHub Actions Workflows、Authentication、GitHub Support Inquiries、Pull Request Practices、Repository Maintenance、GitHub Pages、GitHub Packages、GitHub Discussions、Copilot Spaces + - `query`: 用户关于待解答问题的输入。这是最新、未经编辑的原始用户消息。你必须始终原样保留用户消息，不得修改。（string，必填） -## Read-Only Mode +## 只读模式（Read-Only Mode） -To run the server in read-only mode, you can use the `--read-only` flag. This will only offer read-only tools, preventing any modifications to repositories, issues, pull requests, etc. +要以只读模式运行服务器，可使用 `--read-only` 标志。此模式仅提供只读工具，防止对仓库、议题（issue）、拉取请求（pull request）等进行任何修改。 ```bash ./github-mcp-server --read-only ``` -When using Docker, you can pass the read-only mode as an environment variable: +使用 Docker 时，可将只读模式作为环境变量传入： ```bash docker run -i --rm \ @@ -1556,15 +1561,15 @@ docker run -i --rm \ ghcr.io/github/github-mcp-server ``` -## Lockdown Mode +## 锁定模式（Lockdown Mode） -Lockdown mode limits the content that the server will surface from public repositories. When enabled, the server checks whether the author of each item has push access to the repository. Private repositories are unaffected, and collaborators keep full access to their own content. +锁定模式限制服务器从公开仓库中展示的内容。启用后，服务器会检查每项内容的作者是否对该仓库拥有推送（push）权限。私有仓库不受影响，协作者仍可完全访问自己的内容。 ```bash ./github-mcp-server --lockdown-mode ``` -When running with Docker, set the corresponding environment variable: +使用 Docker 运行时，请设置相应的环境变量： ```bash docker run -i --rm \ @@ -1573,14 +1578,14 @@ docker run -i --rm \ ghcr.io/github/github-mcp-server ``` -The behavior of lockdown mode depends on the tool invoked. +锁定模式的行为取决于所调用的工具。 -Following tools will return an error when the author lacks the push access: +当作者缺少推送权限时，以下工具将返回错误： - `issue_read:get` - `pull_request_read:get` -Following tools will filter out content from users lacking the push access: +以下工具会过滤掉缺少推送权限用户的内容： - `issue_read:get_comments` - `issue_read:get_sub_issues` @@ -1588,13 +1593,11 @@ Following tools will filter out content from users lacking the push access: - `pull_request_read:get_review_comments` - `pull_request_read:get_reviews` -## i18n / Overriding Descriptions +## 国际化 / 覆盖描述（i18n / Overriding Descriptions） -The descriptions of the tools can be overridden by creating a -`github-mcp-server-config.json` file in the same directory as the binary. +可通过在与二进制文件相同目录下创建 `github-mcp-server-config.json` 文件来覆盖工具描述。 -The file should contain a JSON object with the tool names as keys and the new -descriptions as values. For example: +该文件应包含一个 JSON 对象，以工具名称为键、新描述为值。例如： ```json { @@ -1603,42 +1606,33 @@ descriptions as values. For example: } ``` -You can create an export of the current translations by running the binary with -the `--export-translations` flag. +可通过使用 `--export-translations` 标志运行二进制文件来导出当前翻译。 -This flag will preserve any translations/overrides you have made, while adding -any new translations that have been added to the binary since the last time you -exported. +此标志会保留你已做的任何翻译/覆盖，同时添加自上次导出以来二进制文件中新增的翻译。 ```sh ./github-mcp-server --export-translations cat github-mcp-server-config.json ``` -You can also use ENV vars to override the descriptions. The environment -variable names are the same as the keys in the JSON file, prefixed with -`GITHUB_MCP_` and all uppercase. +也可使用环境变量覆盖描述。环境变量名称与 JSON 文件中的键相同，前缀为 `GITHUB_MCP_`，且全部大写。 -For example, to override the `TOOL_ADD_ISSUE_COMMENT_DESCRIPTION` tool, you can -set the following environment variable: +例如，要覆盖 `TOOL_ADD_ISSUE_COMMENT_DESCRIPTION` 工具，可设置以下环境变量： ```sh export GITHUB_MCP_TOOL_ADD_ISSUE_COMMENT_DESCRIPTION="an alternative description" ``` -### Overriding Server Name and Title +### 覆盖服务器名称与标题 -The same override mechanism can be used to customize the MCP server's `name` and -`title` fields in the initialization response. This is useful when running -multiple GitHub MCP Server instances (e.g., one for github.com and one for -GitHub Enterprise Server) so that agents can distinguish between them. +同一覆盖机制可用于自定义 MCP 服务器初始化响应中的 `name` 和 `title` 字段。在运行多个 GitHub MCP Server 实例时（例如一个用于 github.com，一个用于 GitHub Enterprise Server）这很有用，以便代理能够区分它们。 | Key | Environment Variable | Default | |-----|---------------------|---------| | `SERVER_NAME` | `GITHUB_MCP_SERVER_NAME` | `github-mcp-server` | | `SERVER_TITLE` | `GITHUB_MCP_SERVER_TITLE` | `GitHub MCP Server` | -For example, to configure a server instance for GitHub Enterprise Server: +例如，为 GitHub Enterprise Server 配置服务器实例： ```json { @@ -1647,29 +1641,29 @@ For example, to configure a server instance for GitHub Enterprise Server: } ``` -Or using environment variables: +或使用环境变量： ```sh export GITHUB_MCP_SERVER_NAME="ghes-mcp-server" export GITHUB_MCP_SERVER_TITLE="GHES MCP Server" ``` -## Library Usage +## 库用法（Library Usage） -The exported Go API of this module should currently be considered unstable, and subject to breaking changes. In the future, we may offer stability; please file an issue if there is a use case where this would be valuable. +目前应将本模块导出的 Go API 视为不稳定，且可能包含破坏性变更。未来我们可能会提供稳定性保证；若你有相关用例需求，请提交 issue。 -## Contributing +## 贡献（Contributing） -Contributions are welcome. Before opening a pull request, please read the [contributing guide](CONTRIBUTING.md) for setup, testing, linting, and documentation generation instructions. +欢迎贡献。在打开拉取请求之前，请阅读[贡献指南](CONTRIBUTING.md)，了解设置、测试、代码检查（linting）和文档生成说明。 -## Support +## 支持（Support） -For help using the GitHub MCP Server, see the [support guide](SUPPORT.md). If you have found a bug or want to request a feature, please search existing issues before opening a new one. +有关 GitHub MCP Server 的使用帮助，请参阅[支持指南](SUPPORT.md)。若你发现 bug 或想请求新功能，请在新建 issue 前先搜索现有 issue。 -## Security +## 安全（Security） -Please do not report security vulnerabilities through public issues. Follow the instructions in the [security policy](SECURITY.md) to report vulnerabilities responsibly. +请勿通过公开 issue 报告安全漏洞。请按照[安全政策](SECURITY.md)中的说明负责任地报告漏洞。 -## License +## 许可证（License） -This project is licensed under the terms of the MIT open source license. Please refer to [MIT](./LICENSE) for the full terms. +本项目依据 MIT 开源许可证条款授权。完整条款请参阅 [MIT](./LICENSE)。