Using OAuth	Using a GitHub PAT
VS Code (version 1.101 or greater)
\n\n```json\n{\n \"servers\": {\n \"github\": {\n \"type\": \"http\",\n \"url\": \"https://api.githubcopilot.com/mcp/\"\n }\n }\n}\n```\n\n	\n\n```json\n{\n \"servers\": {\n \"github\": {\n \"type\": \"http\",\n \"url\": \"https://api.githubcopilot.com/mcp/\",\n \"headers\": {\n \"Authorization\": \"Bearer ${input:github_mcp_pat}\"\n }\n }\n },\n \"inputs\": [\n {\n \"type\": \"promptString\",\n \"id\": \"github_mcp_pat\",\n \"description\": \"GitHub Personal Access Token\",\n \"password\": true\n }\n ]\n}\n```\n\n

\n\n### Install in other MCP hosts\n\n- **[Copilot CLI](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-copilot-cli.md)** - Installation guide for GitHub Copilot CLI\n- **[GitHub Copilot in other IDEs](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-other-copilot-ides.md)** - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot\n- **[Claude Applications](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-claude.md)** - Installation guide for Claude Desktop and Claude Code CLI\n- **[Codex](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-codex.md)** - Installation guide for OpenAI Codex\n- **[Cursor](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-cursor.md)** - Installation guide for Cursor IDE\n- **[OpenCode](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-opencode.md)** - Installation guide for the OpenCode terminal agent\n- **[Windsurf](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-windsurf.md)** - Installation guide for Windsurf IDE\n- **[Zed](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-zed.md)** - Installation guide for Zed editor\n- **[Rovo Dev CLI](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-rovo-dev-cli.md)** - Installation guide for Rovo Dev CLI\n\n> **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.\n\n### Configuration\n\n#### Toolset configuration\n\nSee [Remote Server Documentation](https://github.com/github/github-mcp-server/blob/main/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.\n\nWhen no toolsets are specified, [default toolsets](#default-toolset) are used.\n\n#### Insiders Mode\n\n> **Try new features early!** The remote server offers an insiders version with early access to new features and experimental tools.\n\n\n\n\n\n\n\n

Using URL Path	Using Header
\n\n```json\n{\n \"servers\": {\n \"github\": {\n \"type\": \"http\",\n \"url\": \"https://api.githubcopilot.com/mcp/insiders\"\n }\n }\n}\n```\n\n	\n\n```json\n{\n \"servers\": {\n \"github\": {\n \"type\": \"http\",\n \"url\": \"https://api.githubcopilot.com/mcp/\",\n \"headers\": {\n \"X-MCP-Insiders\": \"true\"\n }\n }\n }\n}\n```\n\n

\n\nSee [Remote Server Documentation](https://github.com/github/github-mcp-server/blob/main/docs/remote-server.md#insiders-mode) for more details and examples, and [Insiders Features](https://github.com/github/github-mcp-server/blob/main/docs/insiders-features.md) for a full list of what's available.\n\n#### GitHub Enterprise\n\n##### GitHub Enterprise Cloud with data residency (ghe.com)\n\nGitHub Enterprise Cloud can also make use of the remote server.\n\nExample for `https://octocorp.ghe.com` with GitHub PAT token:\n\n```\n{\n ...\n \"github-octocorp\": {\n \"type\": \"http\",\n \"url\": \"https://copilot-api.octocorp.ghe.com/mcp\",\n \"headers\": {\n \"Authorization\": \"Bearer ${input:github_mcp_pat}\"\n }\n },\n ...\n}\n```\n\n> **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)\n\n##### GitHub Enterprise Server\n\nGitHub 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.\n\n---\n\n## Local GitHub MCP Server\n\n[![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)\n\n### Prerequisites\n\n1. To run the server in a container, you will need to have [Docker](https://www.docker.com/) installed.\n2. 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`.\n3. **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](https://github.com/github/github-mcp-server/blob/main/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`).\n\n 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)).\n\n

Handling PATs Securely

\n\n### Environment Variables (Recommended)\n\nTo keep your GitHub PAT secure and reusable across different MCP hosts:\n\n1. **Store your PAT in environment variables**\n\n ```bash\n export GITHUB_PAT=your_token_here\n ```\n\n Or create a `.env` file:\n\n ```env\n GITHUB_PAT=your_token_here\n ```\n\n2. **Protect your `.env` file**\n\n ```bash\n # Add to .gitignore to prevent accidental commits\n echo \".env\" >> .gitignore\n ```\n\n3. **Reference the token in configurations**\n\n ```bash\n # CLI usage\n claude mcp add github -e GITHUB_PERSONAL_ACCESS_TOKEN=$GITHUB_PAT -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-server\n\n # In config files (where supported)\n \"env\": {\n \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"$GITHUB_PAT\"\n }\n ```\n\n> **Note**: Environment variable support varies by host app and IDE. Some applications (like Windsurf) require hardcoded tokens in config files.\n\n### Token Security Best Practices\n\n- **Minimum scopes**: Only grant necessary permissions\n - `repo` - Repository operations\n - `read:packages` - Docker image access\n - `read:org` - Organization team access\n- **Separate tokens**: Use different PATs for different projects/environments\n- **Regular rotation**: Update tokens periodically\n- **Never commit**: Keep tokens out of version control\n- **File permissions**: Restrict access to config files containing tokens\n\n ```bash\n chmod 600 ~/.your-app/config.json\n ```\n\n

\n\n### GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)\n\nThe flag `--gh-host` and the environment variable `GITHUB_HOST` can be used to set\nthe hostname for GitHub Enterprise Server or GitHub Enterprise Cloud with data residency.\n\n- For GitHub Enterprise Server, prefix the hostname with the `https://` URI scheme. HTTPS is required and enforced: non-HTTPS hosts are refused so that credentials are never sent over cleartext (the only exception is a loopback host such as `http://localhost` for local development).\n- For GitHub Enterprise Cloud with data residency, use `https://YOURSUBDOMAIN.ghe.com` as the hostname.\n\n``` json\n\"github\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"-e\",\n \"GITHUB_PERSONAL_ACCESS_TOKEN\",\n \"-e\",\n \"GITHUB_HOST\",\n \"ghcr.io/github/github-mcp-server\"\n ],\n \"env\": {\n \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"${input:github_token}\",\n \"GITHUB_HOST\": \"https://\"\n }\n}\n```\n\n## Installation\n\n### Install in GitHub Copilot on VS Code\n\nFor 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.\n\nMore about using MCP server tools in VS Code's [agent mode documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers).\n\nInstall in GitHub Copilot on other IDEs (JetBrains, Visual Studio, Eclipse, etc.)\n\nAdd one of the following JSON blocks to your IDE's MCP settings.\n\n**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:\n\n```json\n{\n \"mcp\": {\n \"servers\": {\n \"github\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"-p\",\n \"127.0.0.1:8085:8085\",\n \"-e\",\n \"GITHUB_OAUTH_CALLBACK_PORT\",\n \"ghcr.io/github/github-mcp-server\"\n ],\n \"env\": {\n \"GITHUB_OAUTH_CALLBACK_PORT\": \"8085\"\n }\n }\n }\n }\n}\n```\n\nSee **[Local Server OAuth Login](https://github.com/github/github-mcp-server/blob/main/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.\n\nFor non-interactive stdio deployments, see **[GitHub App Authentication](https://github.com/github/github-mcp-server/blob/main/docs/github-app-auth.md)**.\n\n**Or authenticate with a Personal Access Token.** Set `GITHUB_PERSONAL_ACCESS_TOKEN` instead (it takes precedence over OAuth):\n\n```json\n{\n \"mcp\": {\n \"inputs\": [\n {\n \"type\": \"promptString\",\n \"id\": \"github_token\",\n \"description\": \"GitHub Personal Access Token\",\n \"password\": true\n }\n ],\n \"servers\": {\n \"github\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"-e\",\n \"GITHUB_PERSONAL_ACCESS_TOKEN\",\n \"ghcr.io/github/github-mcp-server\"\n ],\n \"env\": {\n \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"${input:github_token}\"\n }\n }\n }\n }\n}\n```\n\nOptionally, 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.\n\n

Example JSON block without the MCP key included

\n
\n\n```json\n{\n \"inputs\": [\n {\n \"type\": \"promptString\",\n \"id\": \"github_token\",\n \"description\": \"GitHub Personal Access Token\",\n \"password\": true\n }\n ],\n \"servers\": {\n \"github\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"-e\",\n \"GITHUB_PERSONAL_ACCESS_TOKEN\",\n \"ghcr.io/github/github-mcp-server\"\n ],\n \"env\": {\n \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"${input:github_token}\"\n }\n }\n }\n}\n```\n\n

\n\n### Install in Other MCP Hosts\n\nFor other MCP host applications, please refer to our installation guides:\n\n- **[Copilot CLI](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-copilot-cli.md)** - Installation guide for GitHub Copilot CLI\n- **[GitHub Copilot in other IDEs](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-other-copilot-ides.md)** - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot\n- **[Claude Code & Claude Desktop](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-claude.md)** - Installation guide for Claude Code and Claude Desktop\n- **[Cursor](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-cursor.md)** - Installation guide for Cursor IDE\n- **[Google Gemini CLI](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-gemini-cli.md)** - Installation guide for Google Gemini CLI\n- **[OpenCode](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-opencode.md)** - Installation guide for the OpenCode terminal agent\n- **[Windsurf](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-windsurf.md)** - Installation guide for Windsurf IDE\n- **[Zed](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides/install-zed.md)** - Installation guide for Zed editor\n\nFor a complete overview of all installation options, see our **[Installation Guides Index](https://github.com/github/github-mcp-server/blob/main/docs/installation-guides)**.\n\n> **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.\n\n### Build from source\n\nIf you don't have Docker, you can use `go build` to build the binary in the\n`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:\n\n```JSON\n{\n \"mcp\": {\n \"servers\": {\n \"github\": {\n \"command\": \"/path/to/github-mcp-server\",\n \"args\": [\"stdio\"],\n \"env\": {\n \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"\"\n }\n }\n }\n }\n}\n```\n\n## Tool Configuration\n\nThe 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.\n\n_Toolsets are not limited to Tools. Relevant MCP Resources and Prompts are also included where applicable._\n\nWhen no toolsets are specified, [default toolsets](#default-toolset) are used.\n\n> **Looking for examples?** See the [Server Configuration Guide](https://github.com/github/github-mcp-server/blob/main/docs/server-configuration.md) for common recipes like minimal setups, read-only mode, and combining tools with toolsets.\n\n#### Specifying Toolsets\n\nTo specify toolsets you want available to the LLM, you can pass an allow-list in two ways:\n\n1. **Using Command Line Argument**:\n\n ```bash\n github-mcp-server --toolsets repos,issues,pull_requests,actions,code_security\n ```\n\n2. **Using Environment Variable**:\n\n ```bash\n GITHUB_TOOLSETS=\"repos,issues,pull_requests,actions,code_security\" ./github-mcp-server\n ```\n\nThe environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided.\n\n#### Specifying Individual Tools\n\nYou can also configure specific tools using the `--tools` flag. Tools can be used independently or combined with toolsets for fine-grained control.\n\n1. **Using Command Line Argument**:\n\n ```bash\n github-mcp-server --tools get_file_contents,issue_read,create_pull_request\n ```\n\n2. **Using Environment Variable**:\n\n ```bash\n GITHUB_TOOLS=\"get_file_contents,issue_read,create_pull_request\" ./github-mcp-server\n ```\n\n3. **Combining with Toolsets** (additive):\n\n ```bash\n github-mcp-server --toolsets repos,issues --tools get_gist\n ```\n\n This registers all tools from `repos` and `issues` toolsets, plus `get_gist`.\n\n**Important Notes:**\n\n- Tools and toolsets can be used together\n- Read-only mode takes priority: write tools are skipped if `--read-only` is set, even if explicitly requested via `--tools`\n- 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\n- When tools are renamed, old names are preserved as aliases for backward compatibility. See [Tool Renaming](https://github.com/github/github-mcp-server/blob/main/docs/tool-renaming.md) for details.\n\n### Using Toolsets With Docker\n\nWhen using Docker, you can pass the toolsets as environment variables:\n\n```bash\ndocker run -i --rm \\\n -e GITHUB_PERSONAL_ACCESS_TOKEN= \\\n -e GITHUB_TOOLSETS=\"repos,issues,pull_requests,actions,code_security\" \\\n ghcr.io/github/github-mcp-server\n```\n\n### Using Tools With Docker\n\nWhen using Docker, you can pass specific tools as environment variables. You can also combine tools with toolsets:\n\n```bash\n# Tools only\ndocker run -i --rm \\\n -e GITHUB_PERSONAL_ACCESS_TOKEN= \\\n -e GITHUB_TOOLS=\"get_file_contents,issue_read,create_pull_request\" \\\n ghcr.io/github/github-mcp-server\n\n# Tools combined with toolsets (additive)\ndocker run -i --rm \\\n -e GITHUB_PERSONAL_ACCESS_TOKEN= \\\n -e GITHUB_TOOLSETS=\"repos,issues\" \\\n -e GITHUB_TOOLS=\"get_gist\" \\\n ghcr.io/github/github-mcp-server\n```\n\n### Special toolsets\n\n#### \"all\" toolset\n\nThe special toolset `all` can be provided to enable all available toolsets regardless of any other configuration:\n\n```bash\n./github-mcp-server --toolsets all\n```\n\nOr using the environment variable:\n\n```bash\nGITHUB_TOOLSETS=\"all\" ./github-mcp-server\n```\n\n#### \"default\" toolset\n\nThe default toolset `default` is the configuration that gets passed to the server if no toolsets are specified.\n\nThe default configuration is:\n\n- context\n- repos\n- issues\n- pull_requests\n- users\n\nTo keep the default configuration and add additional toolsets:\n\n```bash\nGITHUB_TOOLSETS=\"default,stargazers\" ./github-mcp-server\n```\n\n### Insiders Mode\n\nThe local GitHub MCP Server offers an insiders version with early access to new features and experimental tools.\n\n1. **Using Command Line Argument**:\n\n ```bash\n ./github-mcp-server --insiders\n ```\n\n2. **Using Environment Variable**:\n\n ```bash\n GITHUB_INSIDERS=true ./github-mcp-server\n ```\n\nWhen using Docker:\n\n```bash\ndocker run -i --rm \\\n -e GITHUB_PERSONAL_ACCESS_TOKEN= \\\n -e GITHUB_INSIDERS=true \\\n ghcr.io/github/github-mcp-server\n```\n\n### Available Toolsets\n\nThe following sets of tools are available:\n\n\n| | Toolset | Description |\n| --- | ----------------------- | ------------------------------------------------------------- |\n|

| `context` | **Strongly recommended**: Tools that provide context about the current user and GitHub context you are operating in |\n|

| `actions` | GitHub Actions workflows and CI/CD operations |\n|

| `code_quality` | GitHub Code Quality related tools |\n|

| `code_security` | Code security related tools, such as GitHub Code Scanning |\n|

| `copilot` | Copilot related tools |\n|

| `copilot_issue_intents` | Opt-in Copilot issue assignment tools that carry intent metadata (rationale, confidence, suggestion) |\n|

| `dependabot` | Dependabot tools |\n|

| `discussions` | GitHub Discussions related tools |\n|

| `gists` | GitHub Gist related tools |\n|

| `git` | GitHub Git API related tools for low-level Git operations |\n|

| `governance` | Repository governance tools for managing rulesets and custom properties at the repository, organization, and enterprise levels |\n|

| `issues` | GitHub Issues related tools |\n|

| `labels` | GitHub Labels related tools |\n|

| `notifications` | GitHub Notifications related tools |\n|

| `orgs` | GitHub Organization related tools |\n|

| `projects` | GitHub Projects related tools |\n|

| `pull_requests` | GitHub Pull Request related tools |\n|

| `repos` | GitHub Repository related tools |\n|

| `secret_protection` | Secret protection related tools, such as GitHub Secret Scanning |\n|

| `security_advisories` | Security advisories related tools |\n|

| `stargazers` | GitHub Stargazers related tools |\n|

| `users` | GitHub User related tools |\n\n\n### Additional Toolsets in Remote GitHub MCP Server\n\n| Toolset | Description |\n| ----------------------- | ------------------------------------------------------------- |\n| `copilot` | Copilot related tools (e.g. Copilot Coding Agent) |\n| `copilot_spaces` | Copilot Spaces related tools |\n| `github_support_docs_search` | Search docs to answer GitHub product and support questions |\n\n## Tools\n\n\n

\n\n

Actions

\n\n- **actions_get** - Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)\n - **OAuth Challenge Scopes**: `repo`\n - `method`: The method to execute (string, required)\n - `owner`: Repository owner (string, required)\n - `repo`: Repository name (string, required)\n - `resource_id`: The unique identifier of the resource. This will vary based on the \"method\" provided, so ensure you provide the correct ID:\n - Provide a workflow ID or workflow file name (e.g. ci.yaml) for 'get_workflow' method.\n - Provide a workflow run ID for 'get_workflow_run', 'get_workflow_run_usage', and 'get_workflow_run_logs_url' methods.\n - Provide an artifact ID for 'download_workflow_run_artifact' method.\n - Provide a job ID for 'get_workflow_job' method.\n (string, required)\n\n- **actions_list** - List GitHub Actions workflows in a repository\n - **OAuth Challenge Scopes**: `repo`\n - `method`: The action to perform (string, required)\n - `owner`: Repository owner (string, required)\n - `page`: Page number for pagination (default: 1) (number, optional)\n - `perPage`: Results per page for pagination (default: 30, max: 100) (number, optional)\n - `repo`: Repository name (string, required)\n - `resource_id`: The unique identifier of the resource. This will vary based on the \"method\" provided, so ensure you provide the correct ID:\n - Do not provide any resource ID for 'list_workflows' method.\n - 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.\n - Provide a workflow run ID for 'list_workflow_jobs' and 'list_workflow_run_artifacts' methods.\n (string, optional)\n - `workflow_jobs_filter`: Filters for workflow jobs. **ONLY** used when method is 'list_workflow_jobs' (object, optional)\n - `workflow_runs_filter`: Filters for workflow runs. **ONLY** used when method is 'list_workflow_runs' (object, optional)\n\n- **actions_run_trigger** - Trigger GitHub Actions workflow actions\n - **OAuth Challenge Scopes**: `repo`\n - `inputs`: Inputs the workflow accepts. Only used for 'run_workflow' method. (object, optional)\n - `method`: The method to execute (string, required)\n - `owner`: Repository owner (string, required)\n - `ref`: The git reference for the workflow. The reference can be a branch or tag name. Required for 'run_workflow' method. (string, optional)\n - `repo`: Repository name (string, required)\n - `run_id`: The ID of the workflow run. Required for all methods except 'run_workflow'. (number, optional)\n - `workflow_id`: The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml). Required for 'run_workflow' method. (string, optional)\n\n- **get_job_logs** - Get GitHub Actions workflow job logs\n - **OAuth Challenge Scopes**: `repo`\n - `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)\n - `job_id`: The unique identifier of the workflow job. Required when getting logs for a single job. (number, optional)\n - `owner`: Repository owner (string, required)\n - `repo`: Repository name (string, required)\n - `return_content`: Returns actual log content instead of URLs (boolean, optional)\n - `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)\n - `tail_lines`: Number of lines to return from the end of the log (number, optional)\n\n

\n\n

Code Quality

\n\n- **get_code_quality_finding** - Get code quality finding\n - **OAuth Challenge Scopes**: `repo`\n - `findingNumber`: The number of the finding. (number, required)\n - `owner`: The owner of the repository. (string, required)\n - `repo`: The name of the repository. (string, required)\n\n

\n\n

Code Security

\n\n- **get_code_scanning_alert** - Get code scanning alert\n - **OAuth Challenge Scopes**: `security_events`\n - `alertNumber`: The number of the alert. (number, required)\n - `owner`: The owner of the repository. (string, required)\n - `repo`: The name of the repository. (string, required)\n\n- **list_code_scanning_alerts** - List code scanning alerts\n - **OAuth Challenge Scopes**: `security_events`\n - `owner`: The owner of the repository. (string, required)\n - `page`: Page number for pagination (min 1) (number, optional)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `ref`: The Git reference for the results you want to list. (string, optional)\n - `repo`: The name of the repository. (string, required)\n - `severity`: Filter code scanning alerts by severity (string, optional)\n - `state`: Filter code scanning alerts by state. Defaults to open (string, optional)\n - `tool_name`: The name of the tool used for code scanning. (string, optional)\n\n

\n\n

Context

\n\n- **get_me** - Get my user profile\n - No parameters required\n\n- **get_team_members** - Get team members\n - **OAuth Challenge Scopes**: `read:org`\n - `org`: Organization login (owner) that contains the team. (string, required)\n - `team_slug`: Team slug (string, required)\n\n- **get_teams** - Get teams\n - **OAuth Challenge Scopes**: `read:org`\n - `user`: Username to get teams for. If not provided, uses the authenticated user. (string, optional)\n\n

\n\n

Copilot

\n\n- **assign_copilot_to_issue** - Assign Copilot to issue\n - **OAuth Challenge Scopes**: `repo`\n - `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)\n - `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)\n - `issue_number`: Issue number (number, required)\n - `owner`: Repository owner (string, required)\n - `repo`: Repository name (string, required)\n\n- **request_copilot_review** - Request Copilot review\n - **OAuth Challenge Scopes**: `repo`\n - `owner`: Repository owner (string, required)\n - `pullNumber`: Pull request number (number, required)\n - `repo`: Repository name (string, required)\n\n

\n\n

Copilot Issue Intents

\n\n- **assign_copilot_to_issue_with_intent** - Assign Copilot to issue with intent\n - **OAuth Challenge Scopes**: `repo`\n - `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. Ignored when is_suggestion is true (string, optional)\n - `confidence`: How confident you are in this choice. 'HIGH' for clear signal or explicit user request, 'MEDIUM' for reasonable inference with some ambiguity, 'LOW' for best guess with limited signal. (string, required)\n - `custom_instructions`: Optional custom instructions to guide the agent beyond the issue body. Ignored when is_suggestion is true (string, optional)\n - `is_suggestion`: If true, records a pending Copilot assignment intent rather than launching the agent. Approval later supplies the launch context; base_ref and custom_instructions are ignored in this case. (boolean, required)\n - `issue_number`: Issue number (number, required)\n - `owner`: Repository owner (string, required)\n - `rationale`: One concise sentence explaining what specifically about the issue led to choosing Copilot. State the concrete signal (e.g. 'Well-scoped task with clear acceptance criteria'). (string, required)\n - `repo`: Repository name (string, required)\n\n

\n\n

Dependabot

\n\n- **get_dependabot_alert** - Get dependabot alert\n - **OAuth Challenge Scopes**: `security_events`\n - `alertNumber`: The number of the alert. (number, required)\n - `owner`: The owner of the repository. (string, required)\n - `repo`: The name of the repository. (string, required)\n\n- **list_dependabot_alerts** - List dependabot alerts\n - **OAuth Challenge Scopes**: `security_events`\n - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional)\n - `owner`: The owner of the repository. (string, required)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `repo`: The name of the repository. (string, required)\n - `severity`: Filter dependabot alerts by severity (string, optional)\n - `state`: Filter dependabot alerts by state. Defaults to open (string, optional)\n\n

\n\n

Discussions

\n\n- **discussion_comment_write** - Manage discussion comments\n - **OAuth Challenge Scopes**: `repo`\n - `body`: Comment content (required for 'add', 'reply', and 'update' methods) (string, optional)\n - `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)\n - `discussionNumber`: Discussion number (required for 'add' and 'reply' methods) (number, optional)\n - `method`: Write operation to perform on a discussion comment.\n Options are:\n - 'add' - adds a new top-level comment to a discussion.\n - 'reply' - replies to a top-level discussion comment (GitHub Discussions only support one level of nesting).\n - 'update' - updates an existing discussion comment.\n - 'delete' - deletes a discussion comment.\n - 'mark_answer' - marks a discussion comment as the answer (Q&A only).\n - 'unmark_answer' - unmarks a discussion comment as the answer (Q&A only).\n (string, required)\n - `owner`: Repository owner (required for 'add' and 'reply' methods) (string, optional)\n - `repo`: Repository name (required for 'add' and 'reply' methods) (string, optional)\n\n- **get_discussion** - Get discussion\n - **OAuth Challenge Scopes**: `repo`\n - `discussionNumber`: Discussion Number (number, required)\n - `owner`: Repository owner (string, required)\n - `repo`: Repository name (string, required)\n\n- **get_discussion_comments** - Get discussion comments\n - **OAuth Challenge Scopes**: `repo`\n - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional)\n - `discussionNumber`: Discussion Number (number, required)\n - `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)\n - `owner`: Repository owner (string, required)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `repo`: Repository name (string, required)\n\n- **list_discussion_categories** - List discussion categories\n - **OAuth Challenge Scopes**: `repo`\n - `owner`: Repository owner (string, required)\n - `repo`: Repository name. If not provided, discussion categories will be queried at the organisation level. (string, optional)\n\n- **list_discussions** - List discussions\n - **OAuth Challenge Scopes**: `repo`\n - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional)\n - `category`: Optional filter by discussion category ID. If provided, only discussions with this category are listed. (string, optional)\n - `direction`: Order direction. (string, optional)\n - `orderBy`: Order discussions by field. If provided, the 'direction' also needs to be provided. (string, optional)\n - `owner`: Repository owner (string, required)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `repo`: Repository name. If not provided, discussions will be queried at the organisation level. (string, optional)\n\n

\n\n

Gists

\n\n- **create_gist** - Create Gist\n - **OAuth Challenge Scopes**: `gist`\n - `content`: Content for simple single-file gist creation (string, required)\n - `description`: Description of the gist (string, optional)\n - `filename`: Filename for simple single-file gist creation (string, required)\n - `public`: Whether the gist is public (boolean, optional)\n\n- **get_gist** - Get Gist Content\n - `gist_id`: The ID of the gist (string, required)\n\n- **list_gists** - List Gists\n - `page`: Page number for pagination (min 1) (number, optional)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `since`: Only gists updated after this time (ISO 8601 timestamp) (string, optional)\n - `username`: GitHub username (omit for authenticated user's gists) (string, optional)\n\n- **update_gist** - Update Gist\n - **OAuth Challenge Scopes**: `gist`\n - `content`: Content for the file (string, required)\n - `description`: Updated description of the gist (string, optional)\n - `filename`: Filename to update or create (string, required)\n - `gist_id`: ID of the gist to update (string, required)\n\n

\n\n

Git

\n\n- **get_repository_tree** - Get repository tree\n - **OAuth Challenge Scopes**: `repo`\n - `owner`: Repository owner (username or organization) (string, required)\n - `path_filter`: Optional path prefix to filter the tree results (e.g., 'src/' to only show files in the src directory) (string, optional)\n - `recursive`: Setting this parameter to true returns the objects or subtrees referenced by the tree. Default is false (boolean, optional)\n - `repo`: Repository name (string, required)\n - `tree_sha`: The SHA1 value or ref (branch or tag) name of the tree. Defaults to the repository's default branch (string, optional)\n\n

\n\n

Governance

\n\n- **create_repository_ruleset** - Create repository ruleset\n - **OAuth Challenge Scopes**: `repo`, `admin:org`, `admin:enterprise`\n - `bypass_actors`: The actors that can bypass the rules in this ruleset (object[], optional)\n - `conditions`: Conditions for when this ruleset applies, e.g. {\"ref_name\": {\"include\": [\"refs/heads/main\"], \"exclude\": []}} (object, optional)\n - `enforcement`: The enforcement level of the ruleset. 'evaluate' allows admins to test rules before enforcing them (string, required)\n - `enterprise`: Enterprise slug. Required when level is 'enterprise'. (string, optional)\n - `level`: The level at which the ruleset is configured:\n - 'repository': A ruleset on a single repository (requires 'owner' and 'repo').\n - 'organization': A ruleset covering repositories in an organization (requires 'org').\n - 'enterprise': A ruleset covering repositories across an enterprise (requires 'enterprise'). (string, required)\n - `name`: The name of the ruleset (string, required)\n - `org`: Organization name. Required when level is 'organization'. (string, optional)\n - `owner`: Repository owner. Required when level is 'repository'. (string, optional)\n - `repo`: Repository name. Required when level is 'repository'. (string, optional)\n - `rules`: An array of rules within the ruleset. Each rule is an object with a 'type' (e.g. 'creation', 'deletion', 'non_fast_forward', 'required_signatures', 'pull_request', 'required_status_checks') and, for rules that need configuration, a 'parameters' object (object[], required)\n - `target`: The target of the ruleset. Defaults to 'branch'. 'repository' is only valid for 'organization' and 'enterprise' level rulesets. (string, optional)\n\n- **custom_properties_read** - Read custom properties\n - **OAuth Challenge Scopes**: `repo`, `read:org`, `read:enterprise`\n - `enterprise`: Enterprise slug. Required when level is 'enterprise'. (string, optional)\n - `level`: The level at which custom properties are managed:\n - 'repository': The custom property VALUES assigned to a repository (requires 'owner' and 'repo').\n - 'organization': The custom property DEFINITIONS (schema) for an organization (requires 'org').\n - 'enterprise': The custom property DEFINITIONS (schema) for an enterprise (requires 'enterprise'). (string, required)\n - `org`: Organization name. Required when level is 'organization'. (string, optional)\n - `owner`: Repository owner. Required when level is 'repository'. (string, optional)\n - `repo`: Repository name. Required when level is 'repository'. (string, optional)\n\n- **custom_properties_write** - Set custom properties\n - **OAuth Challenge Scopes**: `repo`, `admin:org`, `admin:enterprise`\n - `enterprise`: Enterprise slug. Required when level is 'enterprise'. (string, optional)\n - `level`: The level at which custom properties are managed:\n - 'repository': The custom property VALUES assigned to a repository (requires 'owner' and 'repo').\n - 'organization': The custom property DEFINITIONS (schema) for an organization (requires 'org').\n - 'enterprise': The custom property DEFINITIONS (schema) for an enterprise (requires 'enterprise'). (string, required)\n - `org`: Organization name. Required when level is 'organization'. (string, optional)\n - `owner`: Repository owner. Required when level is 'repository'. (string, optional)\n - `properties`: The custom properties to create or update. At the repository level each item assigns a value ('property_name' and 'value'); at the organization and enterprise levels each item defines the schema ('property_name' and 'value_type', plus optional definition fields). (object[], required)\n - `repo`: Repository name. Required when level is 'repository'. (string, optional)\n\n- **repository_ruleset_read** - Read repository rulesets\n - **OAuth Challenge Scopes**: `repo`, `read:org`, `read:enterprise`\n - `actor_name`: The handle for the GitHub user account to filter rule suites on. Used by the 'list_rule_suites' method. (string, optional)\n - `branch`: Branch name. Required for the 'get_rules_for_branch' method. (string, optional)\n - `enterprise`: Enterprise slug. Required when level is 'enterprise'. (string, optional)\n - `evaluate_status`: Filter rule suites by ruleset evaluation mode. Used by the 'list_rule_suites' method. (string, optional)\n - `includes_parents`: Include rulesets configured at higher levels that also apply. Defaults to true. Used by the 'get' and 'list' methods at the repository level. (boolean, optional)\n - `level`: The level at which the ruleset is configured:\n - 'repository': A ruleset on a single repository (requires 'owner' and 'repo').\n - 'organization': A ruleset covering repositories in an organization (requires 'org').\n - 'enterprise': A ruleset covering repositories across an enterprise (requires 'enterprise'). (string, required)\n - `method`: Operation to perform:\n - 'get': Get a specific ruleset by ID (requires 'ruleset_id'). Supported at every level.\n - 'list': List all rulesets. Supported at every level.\n - 'get_rules_for_branch': Get all rules that apply to a branch (requires 'branch'). Repository level only.\n - 'list_rule_suites': List rule suites, the evaluations of rules against pushes. Repository and organization levels only.\n - 'get_rule_suite': Get a specific rule suite by ID (requires 'rule_suite_id'). Repository and organization levels only. (string, required)\n - `org`: Organization name. Required when level is 'organization'. (string, optional)\n - `owner`: Repository owner. Required when level is 'repository'. (string, optional)\n - `page`: Page number for pagination (min 1) (number, optional)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `ref`: The name of the ref (branch, tag, etc.) to filter rule suites by. Used by the 'list_rule_suites' method. (string, optional)\n - `repo`: Repository name. Required when level is 'repository'. (string, optional)\n - `repository_name`: Repository name to filter rule suites by. Used by the 'list_rule_suites' method at the organization level. (string, optional)\n - `rule_suite_id`: Rule suite ID. Required for the 'get_rule_suite' method. (number, optional)\n - `rule_suite_result`: The rule suite result to filter by. Used by the 'list_rule_suites' method. (string, optional)\n - `ruleset_id`: Ruleset ID. Required for the 'get' method. (number, optional)\n - `time_period`: The time period to filter rule suites by. Used by the 'list_rule_suites' method. (string, optional)\n\n

\n\n

Issues

\n\n- **add_issue_comment** - Add comment to issue or pull request\n - **OAuth Challenge Scopes**: `repo`\n - `body`: Comment content. Required unless reaction is provided. (string, optional)\n - `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. (integer, optional)\n - `issue_number`: Issue or pull request number to comment on or react to. (number, required)\n - `owner`: Repository owner (string, required)\n - `reaction`: Emoji reaction to add. Required unless body is provided. (string, optional)\n - `repo`: Repository name (string, required)\n\n- **get_label** - Get a specific label from a repository\n - **OAuth Challenge Scopes**: `repo`\n - `name`: Label name. (string, required)\n - `owner`: Repository owner (username or organization name) (string, required)\n - `repo`: Repository name (string, required)\n\n- **issue_read** - Get issue details\n - **OAuth Challenge Scopes**: `repo`\n - `issue_number`: The number of the issue (number, required)\n - `method`: The read operation to perform on a single issue.\n Options are:\n 1. get - Get issue details. Also returns best-effort hierarchy flags (`has_parent`, `has_children`); `parent` and `sub_issues_summary` are optional relationship summaries, and `closed_by_pull_requests` summarizes the pull requests configured to close the issue as `total_count` plus up to 5 `references`.\n 2. get_comments - Get issue comments.\n 3. get_sub_issues - Get sub-issues (children) of the issue.\n 4. get_parent - Get the parent issue, if this issue is a sub-issue of another.\n 5. get_labels - Get labels assigned to the issue.\n (string, required)\n - `owner`: The owner of the repository (string, required)\n - `page`: Page number for pagination (min 1) (number, optional)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `repo`: The name of the repository (string, required)\n\n- **issue_write** - Create or update issue/pull request\n - **OAuth Challenge Scopes**: `repo`\n - `assignees`: Usernames to assign to this issue (string[], optional)\n - `body`: Issue body content (string, optional)\n - `duplicate_of`: Issue number that this issue is a duplicate of. Required when state_reason is 'duplicate'. (number, optional)\n - `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)\n - `issue_number`: Issue number to update (number, optional)\n - `labels`: Labels to apply to this issue (string[], optional)\n - `method`: Write operation to perform on a single issue.\n Options are:\n - 'create' - creates a new issue.\n - 'update' - updates an existing issue.\n (string, required)\n - `milestone`: Milestone number (number, optional)\n - `owner`: Repository owner (string, required)\n - `parent_issue_number`: Issue number of the parent issue. Only used when method is 'create' and cannot be combined with issue_fields. The new issue is created and attached to this parent in the same operation. (number, optional)\n - `parent_owner`: Repository owner of the parent issue. Must be provided with parent_repo. Omit both to use owner and repo. Only used when method is 'create' and parent_issue_number is provided. (string, optional)\n - `parent_repo`: Repository name of the parent issue. Must be provided with parent_owner. Omit both to use owner and repo. Only used when method is 'create' and parent_issue_number is provided. (string, optional)\n - `repo`: Repository name (string, required)\n - `state`: New state (string, optional)\n - `state_reason`: Reason for the state change. Ignored unless state is changed. (string, optional)\n - `title`: Issue title (string, optional)\n - `type`: Type of this issue. For updates, pass null to remove the current type. Only use if issue types are enabled for this repository. Use list_issue_types to get valid type values for this repository or its owner organization. If the repository doesn't support issue types, omit this parameter. (string | null, optional)\n\n- **list_issue_fields** - List issue fields\n - **OAuth Challenge Scopes**: `repo`, `read:org`\n - `owner`: The account owner of the repository or organization. The name is not case sensitive. (string, required)\n - `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)\n\n- **list_issue_types** - List available issue types\n - **OAuth Challenge Scopes**: `repo`, `read:org`\n - `owner`: The account owner of the repository or organization. (string, required)\n - `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)\n\n- **list_issues** - List issues\n - **OAuth Challenge Scopes**: `repo`\n - `after`: Cursor for pagination. Use the cursor from the previous response. (string, optional)\n - `direction`: Order direction. If provided, the 'orderBy' also needs to be provided. (string, optional)\n - `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)\n - `fields`: Subset of fields to return for each issue. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting 'body' and 'field_values' in particular drops the largest per-result data. (string[], optional)\n - `labels`: Filter by labels (string[], optional)\n - `orderBy`: Order issues by field. If provided, the 'direction' also needs to be provided. (string, optional)\n - `owner`: Repository owner (string, required)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `repo`: Repository name (string, required)\n - `since`: Filter by date (ISO 8601 timestamp) (string, optional)\n - `state`: Filter by state, by default both open and closed issues are returned when not provided (string, optional)\n\n- **search_issues** - Search issues\n - **OAuth Challenge Scopes**: `repo`\n - `fields`: Subset of fields to return for each issue result. If omitted, all fields are returned. Use this to reduce response size when you only need specific fields; omitting 'body', 'reactions', and 'labels' in particular drops the largest per-result data. (string[], optional)\n - `order`: Sort order (string, optional)\n - `owner`: Optional repository owner. If provided with repo, only issues for this repository are listed. (string, optional)\n - `page`: Page number for pagination (min 1) (number, optional)\n - `perPage`: Results per page for pagination (min 1, max 100) (number, optional)\n - `query`: The search query, as natural language. When the user gives alternative wordings, include them as plain words rather than joining them with OR. (string, required)\n - `repo`: Optional repository name. If provided with owner, only issues for this repository are listed. (string, optional)\n - `sort`: Sort field by number of matches of categories, defaults to best match (string, optional)\n\n- **sub_issue_write** - Change sub-issue\n - **OAuth Challenge Scopes**: `repo`\n - `after_id`: The ID of the sub-issue to be prioritized after (either after_id OR before_id should be specified) (number, optional)\n - `before_id`: The ID of the sub-issue to be prioritized before (either after_id OR before_id should be specified) (number, optional)\n - `issue_number`: The number of the parent issue (number, required)\n - `method`: The action to perform on a single sub-issue\n Options are:\n - 'add' - add a sub-issue to a parent issue in a GitHub repository.\n - 'remove' - remove a sub-issue from a parent issue in a GitHub repository.\n - '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.\n Writes issue hierarchy. To move a sub-issue to a new parent, use `add` with `replace_parent=true`; there is no writable parent field.\n (string, required)\n - `owner`: Repository owner (string, required)\n - `replace_parent`: When true, replaces the sub-issue's current parent issue. Use with 'add' method only. (boolean, optional)\n - `repo`: Repository name (string, required)\n - `sub_issue_id`: The ID of the sub-issue to add. ID is not the same as issue number (number, required)\n\n

\n\n

Labels

\n\n- **get_label** - Get a specific label from a repository\n - **OAuth Challenge Scopes**: `repo`\n - `name`: Label name. (string, required)\n - `owner`: Repository owner (username or organization name) (string, required)\n - `repo`: Repository name (string, required)\n\n- **label_write** - Write operations on repository labels\n - **OAuth Challenge Scopes**: `repo`\n - `color`: Label color as 6-character hex code without '#' prefix (e.g., 'f29513'). Required for 'create', optional for 'update'. (string, optional)\n - `description`: Label description text. Optional for 'create' and 'update'. (string, optional)\n - `met","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"upstream",{"_98":99,"_100":101,"_102":103,"_104":105,"_106":-5,"_107":108},"requiredSecrets",[],"tags",[19],"assets",[],"stats",{"_96":85,"_97":85},"ratingAvg","reviewCount","topics",[19,114,115],"license","MIT","language","Go","registryName","io.github.github/github-mcp-server","homepage","packages",[109],{"_110":111,"_112":113,"_75":-5},"registryType","oci","identifier","ghcr.io/github/github-mcp-server:1.12.0","mcp","mcp-server","ENV",{"_118":119,"_120":121,"_122":123},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]