Omnigit GitHub & Local Git MCP Server
The Omnigit GitHub & Local Git 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.
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.
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.
Fork differences from upstream
This is a fork of github/github-mcp-server with the following additions and improvements.
For the maintained backport checklist, see Fork Differences From Upstream.
Improved review comment ID resolution
get_review_comments now returns a CommentID field (which is the databaseId from GraphQL) alongside the GraphQL NodeID and DatabaseID for every comment node. This CommentID is the numeric ID that should be used when calling add_reply_to_pull_request_comment or pull_request_comment_write. Previously, only the opaque base64 GraphQL node ID was returned, forcing the model to decode it or scrape the numeric ID from comment URLs. The commentId / comment_id parameter descriptions in those tools now explicitly say to use the CommentID field.
Issue comment management (issue_comment_write)
A new issue_comment_write tool lets AI agents update or delete existing issue comments. Previously only add_issue_comment (create) was available.
PR review comment management (pull_request_comment_write)
A new pull_request_comment_write tool lets AI agents update or delete existing pull request review comments.
Body filtering (filter_patterns)
Issue bodies, PR bodies, and local git commit messages are filtered before being sent to GitHub. By default, Co-Authored-By: trailers and generic AI-generated PR footers are stripped. The filter list is fully configurable via filter_patterns in omnigit-mcp-config.json. See i18n / Overriding Descriptions for details.
Local Git toolset (local_git)
A full set of git_* tools for operating on local repositories without going through the GitHub API: git_add, git_apply_patch_file, git_apply_patch_string, git_checkout, git_commit, git_create_branch, git_diff, git_diff_staged, git_diff_unstaged, git_init, git_list_repositories, git_log, git_pull, git_push, git_reset, git_show, and git_status.
Remote GitHub MCP Server
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 instead.
Prerequisites
- A compatible MCP host with remote server support (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, etc.)
- Any applicable policies enabled
Install in 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 or later for remote MCP and OAuth support.
Alternatively, to manually configure VS Code, choose the appropriate JSON block from the examples below and add it to your host configuration:
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/",
"headers": {
"Authorization": "Bearer ${input:github_mcp_pat}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "github_mcp_pat",
"description": "GitHub Personal Access Token",
"password": true
}
]
}
Install in other MCP hosts
- Copilot CLI - Installation guide for GitHub Copilot CLI
- GitHub Copilot in other IDEs - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
- Claude Applications - Installation guide for Claude Desktop and Claude Code CLI
- Codex - Installation guide for OpenAI Codex
- Cursor - Installation guide for Cursor IDE
- OpenCode - Installation guide for the OpenCode terminal agent
- Windsurf - Installation guide for Windsurf IDE
- Zed - Installation guide for Zed editor
- Rovo Dev CLI - Installation guide for 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.
Configuration
Toolset configuration
See Remote Server Documentation 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.
When no toolsets are specified, default toolsets are used.
Insiders Mode
Try new features early! The remote server offers an insiders version with early access to new features and experimental tools.
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/insiders"
}
}
}
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/",
"headers": {
"X-MCP-Insiders": "true"
}
}
}
}
See Remote Server Documentation for more details and examples, and Insiders Features for a full list of what's available.
GitHub Enterprise
GitHub Enterprise Cloud with data residency (ghe.com)
GitHub Enterprise Cloud can also make use of the remote server.
Example for https://octocorp.ghe.com with GitHub PAT token:
{
...
"github-octocorp": {
"type": "http",
"url": "https://copilot-api.octocorp.ghe.com/mcp",
"headers": {
"Authorization": "Bearer ${input:github_mcp_pat}"
}
},
...
}
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
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) from the local server configuration.
Local GitHub MCP Server
Prerequisites
-
To run the server in a container, you will need to have Docker installed.
-
Once Docker is installed, you will also need to ensure Docker is running. The Docker image is available at
ghcr.io/aifity/omnigit-mcp. The image is public; if you get errors on pull, you may have an expired token and need todocker logout ghcr.io. -
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 for how it works, headless/device-code fallback, and bringing your own OAuth or GitHub App (required for GitHub Enterprise Server andghe.com).Prefer a token? You can still authenticate with a GitHub Personal Access Token by setting
GITHUB_PERSONAL_ACCESS_TOKENinstead (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).
Environment Variables (Recommended)
To keep your GitHub PAT secure and reusable across different MCP hosts:
-
Store your PAT in environment variables
export GITHUB_PAT=your_token_hereOr create a
.envfile:GITHUB_PAT=your_token_here -
Protect your
.envfile# Add to .gitignore to prevent accidental commits echo ".env" >> .gitignore -
Reference the token in configurations
# CLI usage claude mcp add github -e GITHUB_PERSONAL_ACCESS_TOKEN=$GITHUB_PAT -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/aifity/omnigit-mcp # In config files (where supported) "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "$GITHUB_PAT" }
Note: Environment variable support varies by host app and IDE. Some applications (like Windsurf) require hardcoded tokens in config files.
Token Security Best Practices
-
Minimum scopes: Only grant necessary permissions
repo- Repository operationsread:packages- Docker image accessread: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
chmod 600 ~/.your-app/config.json
GitHub Enterprise Server and Enterprise Cloud with data residency (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.
- For GitHub Enterprise Server, prefix the hostname with the
https://URI scheme, as it otherwise defaults tohttp://, which GitHub Enterprise Server does not support. - For GitHub Enterprise Cloud with data residency, use
https://YOURSUBDOMAIN.ghe.comas the hostname.
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"-e",
"GITHUB_HOST",
"ghcr.io/aifity/omnigit-mcp"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}",
"GITHUB_HOST": "https://<your GHES or ghe.com domain name>"
}
}
Installation
Install in GitHub Copilot on 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.
More about using MCP server tools in VS Code's agent mode documentation.
Install in GitHub Copilot on other IDEs (JetBrains, Visual Studio, Eclipse, etc.)
Add one of the following JSON blocks to your IDE's MCP settings.
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:
{
"mcp": {
"servers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-p",
"127.0.0.1:8085:8085",
"-e",
"GITHUB_OAUTH_CALLBACK_PORT",
"ghcr.io/aifity/omnigit-mcp"
],
"env": {
"GITHUB_OAUTH_CALLBACK_PORT": "8085"
}
}
}
}
}
See Local Server OAuth Login 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.
Or authenticate with a Personal Access Token. Set GITHUB_PERSONAL_ACCESS_TOKEN instead (it takes precedence over OAuth):
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "github_token",
"description": "GitHub Personal Access Token",
"password": true
}
],
"servers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/aifity/omnigit-mcp"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}"
}
}
}
}
}
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.
{
"inputs": [
{
"type": "promptString",
"id": "github_token",
"description": "GitHub Personal Access Token",
"password": true
}
],
"servers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/aifity/omnigit-mcp"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}"
}
}
}
}
Install in Other MCP Hosts
For other MCP host applications, please refer to our installation guides:
- Copilot CLI - Installation guide for GitHub Copilot CLI
- GitHub Copilot in other IDEs - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
- Claude Code & Claude Desktop - Installation guide for Claude Code and Claude Desktop
- Cursor - Installation guide for Cursor IDE
- Google Gemini CLI - Installation guide for Google Gemini CLI
- OpenCode - Installation guide for the OpenCode terminal agent
- Windsurf - Installation guide for Windsurf IDE
- Zed - Installation guide for Zed editor
For a complete overview of all installation options, see our Installation Guides Index.
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.
Build from source
If you don't have Docker, you can use go build to build the binary in the
cmd/omnigit-mcp directory, and use the omnigit-mcp 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:
{
"mcp": {
"servers": {
"github": {
"command": "/path/to/omnigit-mcp",
"args": ["stdio"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
}
CLI utilities
The omnigit-mcp binary includes a few CLI subcommands that are helpful for debugging and exploring the server.
omnigit-mcp tool-search "<query>"searches tools by name, description, and input parameter names. Use--max-resultsto return more matches. Example (color output requires a TTY; usedocker run -t(or-it) when running in Docker):
docker run -it --rm ghcr.io/aifity/omnigit-mcp tool-search "issue" --max-results 5
omnigit-mcp 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.
Toolsets are not limited to Tools. Relevant MCP Resources and Prompts are also included where applicable.
When no toolsets are specified, default toolsets are used.
Looking for examples? See the Server Configuration Guide for common recipes like minimal setups, read-only mode, and combining tools with toolsets.
Specifying Toolsets
To specify toolsets you want available to the LLM, you can pass an allow-list in two ways:
-
Using Command Line Argument:
omnigit-mcp --toolsets repos,issues,pull_requests,actions,code_security -
Using Environment Variable:
GITHUB_TOOLSETS="repos,issues,pull_requests,actions,code_security" ./omnigit-mcp
The environment variable GITHUB_TOOLSETS takes precedence over the command line argument if both are provided.
Specifying Individual Tools
You can also configure specific tools using the --tools flag. Tools can be used independently or combined with toolsets for fine-grained control.
-
Using Command Line Argument:
omnigit-mcp --tools get_file_contents,issue_read,create_pull_request -
Using Environment Variable:
GITHUB_TOOLS="get_file_contents,issue_read,create_pull_request" ./omnigit-mcp -
Combining with Toolsets (additive):
omnigit-mcp --toolsets repos,issues --tools get_gistThis registers all tools from
reposandissuestoolsets, plusget_gist.
Important Notes:
- Tools and toolsets can be used together
- Read-only mode takes priority: write tools are skipped if
--read-onlyis set, even if explicitly requested via--tools - Tool names must match exactly (e.g.,
get_file_contents, notgetFileContents). 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 for details.
Using Toolsets With Docker
When using Docker, you can pass the toolsets as environment variables:
docker run -i --rm \
-e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
-e GITHUB_TOOLSETS="repos,issues,pull_requests,actions,code_security" \
ghcr.io/aifity/omnigit-mcp
Using Tools With Docker
When using Docker, you can pass specific tools as environment variables. You can also combine tools with toolsets:
# Tools only
docker run -i --rm \
-e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
-e GITHUB_TOOLS="get_file_contents,issue_read,create_pull_request" \
ghcr.io/aifity/omnigit-mcp
# Tools combined with toolsets (additive)
docker run -i --rm \
-e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
-e GITHUB_TOOLSETS="repos,issues" \
-e GITHUB_TOOLS="get_gist" \
ghcr.io/aifity/omnigit-mcp
Special toolsets
"all" toolset
The special toolset all can be provided to enable all available toolsets regardless of any other configuration:
./omnigit-mcp --toolsets all
Or using the environment variable:
GITHUB_TOOLSETS="all" ./omnigit-mcp
"default" toolset
The default toolset default is the configuration that gets passed to the server if no toolsets are specified.
The default configuration is:
- context
- repos
- issues
- pull_requests
- users
To keep the default configuration and add additional toolsets:
GITHUB_TOOLSETS="default,stargazers" ./omnigit-mcp
Insiders Mode
The local GitHub MCP Server offers an insiders version with early access to new features and experimental tools.
-
Using Command Line Argument:
./omnigit-mcp --insiders -
Using Environment Variable:
GITHUB_INSIDERS=true ./omnigit-mcp
When using Docker:
docker run -i --rm \
-e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
-e GITHUB_INSIDERS=true \
ghcr.io/aifity/omnigit-mcp
Available Toolsets
The following sets of tools are available:
Additional Toolsets in Remote GitHub MCP Server
Tools
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
- 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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
get_me - Get my user profile
- No parameters required
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
get_discussion - Get discussion
- Required OAuth Scopes:
repo discussionNumber: Discussion Number (number, required)owner: Repository owner (string, required)repo: Repository name (string, required)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
get_gist - Get Gist Content
gist_id: The ID of the gist (string, required)
-
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)
-
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)
- Required OAuth Scopes:
- 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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
get_label - Get a specific label from a repository
- Required OAuth Scopes:
repo name: Label name. (string, required)owner: Repository owner (username or organization name) (string, required)repo: Repository name (string, required)
- Required OAuth Scopes:
-
issue_comment_write - Update or delete issue comment
- Required OAuth Scopes:
repo body: New comment content (required for update method) (string, optional)comment_id: Comment ID to update or delete (number, required)method: The write operation to perform on a comment. Options are:- 'update' - updates an existing comment.
- 'delete' - deletes an existing comment. (string, required)
owner: Repository owner (string, required)repo: Repository name (string, required)
- Required OAuth Scopes:
-
issue_read - Get issue details
- 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:- get - Get issue details. Also returns best-effort hierarchy flags (
has_parent,has_children);parentandsub_issues_summaryare optional relationship summaries.
- get - Get issue details. Also returns best-effort hierarchy flags (
- Required OAuth Scopes:
-
get_label - Get a specific label from a repository
- Required OAuth Scopes:
repo name: Label name. (string, required)owner: Repository owner (username or organization name) (string, required)repo: Repository name (string, required)
- Required OAuth Scopes:
-
label_write - Write operations on repository labels
- 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)
- Required OAuth Scopes:
-
list_label - List labels from a repository
- 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)
- Required OAuth Scopes:
-
git_add - Git add
files: Comma-separated list of file paths to stage (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_add - Git add
files: Comma-separated list of file paths to stage (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_apply_patch_file - Git apply patch file
patch_file: Path to the patch file (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_apply_patch_file - Git apply patch file
patch_file: Path to the patch file (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_apply_patch_string - Git apply patch string
patch_string: Patch string to apply (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_apply_patch_string - Git apply patch string
patch_string: Patch string to apply (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_checkout - Git checkout
branch_name: Name of branch to checkout (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_checkout - Git checkout
branch_name: Name of branch to checkout (string, required)repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
-
git_commit - Git commit
message: Commit message (string, required)
-
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)
- Required OAuth Scopes:
-
get_notification_details - Get notification details
- Required OAuth Scopes:
notifications notificationID: The ID of the notification (string, required)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
- 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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
-
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)
- Required OAuth Scopes:
