mcp github

Local 2025-08-31 23:33:58 0

Anthropic's github MCP server, but better. Support for more endpoints. Including releases and tags, pull request reviews, statuses, rate limit, gists, projects, packages, and even pull request diffs. Indented to be used with MissionSquad's MCP API for secret management (aka your access token).


MCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.

Mission Squad modifications

  • github pat is now dynamic per request and does not have to be included via environment variables, but still falls back to environment variables.
  • name: mcp-github

Features

  • Automatic Branch Creation: When creating/updating files or pushing changes, branches are automatically created if they Do not exist
  • Comprehensive Error Handling: Clear error messages for common issues
  • Git History Preservation: Operations maintain proper Git history without force pushing
  • Batch Operations: Support for both single-file and multi-file operations
  • Advanced Search: Support for searching code, issues/PRs, and users

Tools

  1. create_or_update_file
  2. Create or update a single file in a repository
  3. Inputs:
    • owner (string): Repository owner (username or organization)
    • repo (string): Repository name
    • path (string): Path where to create/update the file
    • content (string): Content of the file
    • message (string): Commit message
    • branch (string): Branch to create/update the file in
    • sha (optional string): SHA of file being replaced (for updates)
  4. Returns: File content and commit details

  5. push_files

  6. Push multiple files in a single commit
  7. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • branch (string): Branch to push to
    • files (array): Files to push, each with path and content
    • message (string): Commit message
  8. Returns: Updated branch reference

  9. search_repositories

  10. Search for GitHub repositories
  11. Inputs:
    • query (string): Search query
    • page (optional number): Page number for pagination
    • perPage (optional number): Results per page (max 100)
  12. Returns: Repository search results

  13. create_repository

  14. Create a new GitHub repository
  15. Inputs:
    • name (string): Repository name
    • description (optional string): Repository description
    • private (optional boolean): Whether repo should be private
    • autoInit (optional boolean): Initialize with README
  16. Returns: Created repository details

  17. get_file_contents

  18. Get contents of a file or directory
  19. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • path (string): Path to file/directory
    • branch (optional string): Branch to get contents from
  20. Returns: File/directory contents

  21. create_issue

  22. Create a new issue
  23. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • title (string): Issue title
    • body (optional string): Issue description
    • assignees (optional string[]): Usernames to assign
    • labels (optional string[]): Labels to add
    • milestone (optional number): Milestone number
  24. Returns: Created issue details

  25. create_pull_request

  26. Create a new pull request
  27. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • title (string): PR title
    • body (optional string): PR description
    • head (string): Branch containing changes
    • base (string): Branch to merge into
    • draft (optional boolean): Create as draft PR
    • maintainer_can_modify (optional boolean): Allow maintainer edits
  28. Returns: Created pull request details

  29. fork_repository

  30. Fork a repository
  31. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • organization (optional string): Organization to fork to
  32. Returns: Forked repository details

  33. create_branch

  34. Create a new branch
  35. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • branch (string): Name for new branch
    • from_branch (optional string): Source branch (defaults to repo default)
  36. Returns: Created branch reference

  37. list_issues

    • List and filter repository issues
    • Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • state (optional string): Filter by state ('open', 'closed', 'all')
    • labels (optional string[]): Filter by labels
    • sort (optional string): Sort by ('created', 'updated', 'comments')
    • direction (optional string): Sort direction ('asc', 'desc')
    • since (optional string): Filter by date (ISO 8601 timestamp)
    • page (optional number): Page number
    • per_page (optional number): Results per page
    • Returns: Array of issue details
  38. update_issue

    • Update an existing issue
    • Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • issue_number (number): Issue number to update
    • title (optional string): New title
    • body (optional string): New description
    • state (optional string): New state ('open' or 'closed')
    • labels (optional string[]): New labels
    • assignees (optional string[]): New assignees
    • milestone (optional number): New milestone number
    • Returns: Updated issue details
  39. add_issue_comment

    • Add a comment to an issue
    • Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • issue_number (number): Issue number to comment on
    • body (string): Comment text
    • Returns: Created comment details
  40. search_code

    • Search for code across GitHub repositories
    • Inputs:
    • q (string): Search query using GitHub code search syntax
    • sort (optional string): Sort field ('indexed' only)
    • order (optional string): Sort order ('asc' or 'desc')
    • per_page (optional number): Results per page (max 100)
    • page (optional number): Page number
    • Returns: Code search results with repository context
  41. search_issues

    • Search for issues and pull requests
    • Inputs:
    • q (string): Search query using GitHub issues search syntax
    • sort (optional string): Sort field (comments, reactions, created, etc.)
    • order (optional string): Sort order ('asc' or 'desc')
    • per_page (optional number): Results per page (max 100)
    • page (optional number): Page number
    • Returns: Issue and pull request search results
  42. search_users

    • Search for GitHub users
    • Inputs:
    • q (string): Search query using GitHub users search syntax
    • sort (optional string): Sort field (followers, repositories, joined)
    • order (optional string): Sort order ('asc' or 'desc')
    • per_page (optional number): Results per page (max 100)
    • page (optional number): Page number
    • Returns: User search results
  43. list_commits

  44. Gets commits of a branch in a repository
  45. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • page (optional string): page number
    • per_page (optional string): number of record per page
    • sha (optional string): branch name
  46. Returns: List of commits

  47. get_issue

  48. Gets the contents of an issue within a repository
  49. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • issue_number (number): Issue number to retrieve
  50. Returns: Github Issue object & details

  51. get_pull_request

  52. Get details of a specific pull request
  53. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
  54. Returns: Pull request details including diff and review status

  55. list_pull_requests

  56. List and filter repository pull requests
  57. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • state (optional string): Filter by state ('open', 'closed', 'all')
    • head (optional string): Filter by head user/org and branch
    • base (optional string): Filter by base branch
    • sort (optional string): Sort by ('created', 'updated', 'popularity', 'long-running')
    • direction (optional string): Sort direction ('asc', 'desc')
    • per_page (optional number): Results per page (max 100)
    • page (optional number): Page number
  58. Returns: Array of pull request details

  59. create_pull_request_review

  60. Create a review on a pull request
  61. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
    • body (string): Review comment text
    • event (string): Review action ('APPROVE', 'REQUEST_CHANGES', 'COMMENT')
    • commit_id (optional string): SHA of commit to review
    • comments (optional array): Line-specific comments, each with:
    • path (string): File path
    • position (number): Line position in diff
    • body (string): Comment text
  62. Returns: Created review details

  63. merge_pull_request

  64. Merge a pull request
  65. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
    • commit_title (optional string): Title for merge commit
    • commit_message (optional string): Extra detail for merge commit
    • merge_method (optional string): Merge method ('merge', 'squash', 'rebase')
  66. Returns: Merge result details

  67. get_pull_request_files

  68. Get the list of files changed in a pull request
  69. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
  70. Returns: Array of changed files with patch and status details

  71. get_pull_request_status

  72. Get the combined status of all status checks for a pull request
  73. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
  74. Returns: Combined status check results and individual check details

  75. update_pull_request_branch

  76. Update a pull request branch with the latest changes from the base branch (equivalent to GitHub's "Update branch" button)
  77. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
    • expected_head_sha (optional string): The expected SHA of the pull request's HEAD ref
  78. Returns: Success message when branch is updated

  79. get_pull_request_comments

  80. Get the review comments on a pull request
  81. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
  82. Returns: Array of pull request review comments with details like the comment text, author, and location in the diff

  83. get_pull_request_reviews

  84. Get the reviews on a pull request
  85. Inputs:
    • owner (string): Repository owner
    • repo (string): Repository name
    • pull_number (number): Pull request number
  86. Returns: Array of pull request reviews with details like the review state (APPROVED, CHANGES_REQUESTED, etc.), reviewer, and review body

Search Query Syntax

  • language:javascript: Search by programming language
  • repo:owner/name: Search in specific repository
  • path:app/src: Search in specific path
  • extension:js: Search by file extension
  • Example: q: "import express" language:typescript path:src/
  • is:issue or is:pr: Filter by type
  • is:open or is:closed: Filter by state
  • label:bug: Search by label
  • author:username: Search by author
  • Example: q: "memory leak" is:issue is:open label:bug
  • type:user or type:org: Filter by account type
  • followers:>1000: Filter by followers
  • location:London: Search by location
  • Example: q: "fullstack developer" location:London followers:>100

For detailed search syntax, see GitHub's searching documentation.

Setup

Personal Access Token

Create a GitHub Personal Access Token with appropriate permissions: - Go to Personal access tokens (in GitHub Settings > Developer settings) - Select which repositories you'd like this token to have access to (Public, All, or Select) - Create a token with the repo scope ("Full control of private repositories") - Alternatively, if working only with public repositories, select only the public_repo scope - Copy the generated token

Usage with Claude Desktop

To use this with Claude Desktop, add the following to your claude_desktop_config.json:

Docker

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "mcp/github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

NPX

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Build

Docker build:

docker build -t mcp/github -f src/github/Dockerfile .

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.