Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.
Use cases
01Repository Management: Browse and query code, search files, analyze commits, and understand project structure across any repository you have access to.
02Issue & PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards.
03CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, manage releases, and get insights into your development pipeline.
04Code Analysis: Examine security findings, review Dependabot alerts, understand code patterns, and get comprehensive insights into your codebase.
05Team Collaboration: Access discussions, manage notifications, analyze team activity, and streamline processes for your team.
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.
get_review_comments now returns a CommentID field (which is the databaseId from GraphQL) alongside the GraphQL NodeID and for every comment node. This is the numeric ID that should be used when calling or . 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 / parameter descriptions in those tools now explicitly say to use the field.
No FAQ yet. Enrichment fills this from the README on the next crawl.
Tools (24)
actions_get
Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)
actions_list
List GitHub Actions workflows in a repository
actions_run_trigger
Trigger GitHub Actions workflow actions
assign_copilot_to_issue
Assign Copilot to issue
create_gist
Create Gist
discussion_comment_write
Manage discussion comments
get_code_quality_finding
Get code quality finding
get_code_scanning_alert
Get code scanning alert
get_dependabot_alert
Get dependabot alert
get_discussion
Get discussion
get_discussion_comments
Get discussion comments
get_gist
Get Gist Content
get_job_logs
Get GitHub Actions workflow job logs
get_me
Get my user profile
get_repository_tree
Get repository tree
get_team_members
Get team members
get_teams
Get teams
list_code_scanning_alerts
List code scanning alerts
list_dependabot_alerts
List dependabot alerts
list_discussion_categories
List discussion categories
list_discussions
List discussions
list_gists
List Gists
request_copilot_review
Request Copilot review
update_gist
Update Gist
DatabaseID
CommentID
add_reply_to_pull_request_comment
pull_request_comment_write
commentId
comment_id
CommentID
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.
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.)
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:
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.
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
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 to docker 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 and ghe.com).
Prefer a token? You can still authenticate with a GitHub Personal Access Token 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).
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_here
Or create a .env file:
GITHUB_PAT=your_token_here
Protect your .env file
# 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 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
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 to http://, which GitHub Enterprise Server does not support.
For GitHub Enterprise Cloud with data residency, use https://YOURSUBDOMAIN.ghe.com as the hostname.
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.
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:
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):
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.
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:
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-results to return more matches.
Example (color output requires a TTY; use docker run -t (or -it) when running in Docker):
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.
This registers all tools from repos and issues toolsets, plus 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 for details.
Using Toolsets With Docker
When using Docker, you can pass the toolsets as environment variables:
user: Username to get teams for. If not provided, uses the authenticated user. (string, optional)
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)
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)
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)
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)
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)
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_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)
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_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)
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)
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)
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)
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)
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)
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)
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); parent and sub_issues_summary are optional relationship summaries.
get_comments - Get issue comments.
get_sub_issues - Get sub-issues (children) of the issue.
get_parent - Get the parent issue, if this issue is a sub-issue of another.
get_labels - Get labels assigned to the 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)
issue_write - Create or update 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.
(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)
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: 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)
list_issues - List 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)
search_issues - Search 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)
sub_issue_write - Change sub-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.
(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)
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)
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)
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)
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)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_commit - Git commit
message: Commit message (string, required)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_create_branch - Git create branch
base_branch: Starting point for the new branch (optional) (string, optional)
branch_name: Name of the new branch (string, required)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_create_branch - Git create branch
base_branch: Starting point for the new branch (optional) (string, optional)
branch_name: Name of the new branch (string, required)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_diff - Git diff
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
target: Target branch or commit to compare with (string, required)
git_diff - Git diff
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
target: Target branch or commit to compare with (string, required)
git_diff_staged - Git diff staged
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_diff_staged - Git diff staged
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_diff_unstaged - Git diff unstaged
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_diff_unstaged - Git diff unstaged
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_init - Git init
repo_path: Path to directory to initialize git repo (string, required)
git_init - Git init
repo_path: Path to directory to initialize git repo (string, required)
git_list_repositories - Git list repositories
No parameters required
git_list_repositories - Git list repositories
No parameters required
git_log - Git log
max_count: Maximum number of commits to show (default: 10) (number, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_log - Git log
max_count: Maximum number of commits to show (default: 10) (number, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_pull - Git pull
branch: Branch name to pull (default: current branch's upstream) (string, optional)
remote: Remote name (default: origin) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_pull - Git pull
branch: Branch name to pull (default: current branch's upstream) (string, optional)
remote: Remote name (default: origin) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_push - Git push
branch: Branch name to push (default: current branch) (string, optional)
remote: Remote name (default: origin) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_push - Git push
branch: Branch name to push (default: current branch) (string, optional)
remote: Remote name (default: origin) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_reset - Git reset
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_reset - Git reset
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_show - Git show
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
revision: The revision (commit hash, branch name, tag) to show (string, required)
git_show - Git show
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
revision: The revision (commit hash, branch name, tag) to show (string, required)
git_status - Git status
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_status - Git status
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_worktree_add - Git worktree add
commitish: Branch name, tag, or commit SHA to checkout in the new worktree (optional) (string, optional)
detach: Create a detached HEAD worktree (optional, default: false) (boolean, optional)
force: Force creation even if worktree path already exists (optional, default: false) (boolean, optional)
new_branch: Create a new branch with this name in the worktree (optional) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree_path: Path where the new worktree should be created (string, required)
git_worktree_add - Git worktree add
commitish: Branch name, tag, or commit SHA to checkout in the new worktree (optional) (string, optional)
detach: Create a detached HEAD worktree (optional, default: false) (boolean, optional)
force: Force creation even if worktree path already exists (optional, default: false) (boolean, optional)
new_branch: Create a new branch with this name in the worktree (optional) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree_path: Path where the new worktree should be created (string, required)
git_worktree_list - Git worktree list
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_worktree_list - Git worktree list
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
git_worktree_lock - Git worktree lock
reason: Reason for locking the worktree (optional) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to lock (string, required)
git_worktree_lock - Git worktree lock
reason: Reason for locking the worktree (optional) (string, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to lock (string, required)
git_worktree_prune - Git worktree prune
dry_run: Show what would be pruned without actually pruning (optional, default: false) (boolean, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
verbose: Show verbose output (optional, default: false) (boolean, optional)
git_worktree_prune - Git worktree prune
dry_run: Show what would be pruned without actually pruning (optional, default: false) (boolean, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
verbose: Show verbose output (optional, default: false) (boolean, optional)
git_worktree_remove - Git worktree remove
force: Force removal even if worktree is dirty or locked (optional, default: false) (boolean, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to remove (string, required)
git_worktree_remove - Git worktree remove
force: Force removal even if worktree is dirty or locked (optional, default: false) (boolean, optional)
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to remove (string, required)
git_worktree_unlock - Git worktree unlock
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to unlock (string, required)
git_worktree_unlock - Git worktree unlock
repo_path: Path to Git repository (optional if default repository is configured) (string, optional)
worktree: Path to the worktree directory to unlock (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)
get_notification_details - Get notification details
Required OAuth Scopes: notifications
notificationID: The ID of the notification (string, required)
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)
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)
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_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_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)