---

name: github category: integration-connectivity/mcp-integrations version: 1.0.0 description: Complete guide to using GitHub MCP server with Claude Code author: blackbox5/mcp verified: true tags: [mcp, github, repository, issues, pr]

GitHub MCP Server Skills

Configuration: HTTP endpoint at https://api.githubcopilot.com/mcp/

Requires: GitHub Personal Access Token (PAT)

For destructive operations (delete, merge, close), Claude will ask for confirmation. Always verify repository names and branches before making changes.

<available_skills> <skill_group name="Repository Management"> List repositories accessible to your account List all my repositories Sort by (updated, created, full_name) Results per page (default: 30) Filter by owner, collaborator, organization_member Get details of a specific repository Get details for repo shaansisodia/lumelle Repository owner Repository name Repository description, stars, forks, watchers, default branch, language statistics, last updated date Create a new repository Create a new repository called my-new-repo Repository name (required) Repository description Visibility (true/false) Initialize with README .gitignore template License template Update repository settings Update repository description for lumelle Repository owner Repository name Fields to update Delete a repository Delete repository test-repo This action cannot be undone! </skill_group>

<skill_group name="Branch Management"> List branches in a repository List all branches in lumelle Get details of a specific branch Get details for branch dev in lumelle Branch name, commit SHA, commit message, author information Create a new branch Create branch feature/new-ui from main New branch name Base branch (default: main) Delete a branch Delete branch feature/old-feature </skill_group>

<skill_group name="Issue Management"> List issues in a repository List all open issues in lumelle Issue state (open, closed, all) Filter by labels Filter by assignee Filter by creator Sort by (created, updated, comments) Get details of a specific issue Get issue #123 in lumelle Issue title and body, labels and assignees, comments, state (open/closed), created/closed dates Create a new issue Create an issue titled 'Fix login bug' with description ... Issue title (required) Issue description (supports markdown) Array of label names Array of usernames Milestone number Update an existing issue Update issue #123 to add label 'bug' Issue number Fields to update Get comments on an issue Get comments for issue #123 Add a comment to an issue Comment on issue #123: 'This is fixed' </skill_group>

<skill_group name="Pull Request Management"> List pull requests in a repository List all open PRs in lumelle PR state (open, closed, all) Filter by head branch Filter by base branch Sort by (created, updated, popularity) Get details of a specific PR Get PR #42 in lumelle PR title and body, branch names (head/base), status (open/closed/merged), review status, mergeable status, commits and files changed Create a new pull request Create a PR from feature/new-ui to main PR title (required) Head branch (required) Base branch (default: main) PR description (supports markdown) Create as draft PR Update an existing PR Update PR #42 to add reviewer Get files changed in a PR Show files changed in PR #42 Get review comments on a PR Get comments for PR #42 Create a review on a PR Approve PR #42 Review action (APPROVE, REQUEST_CHANGES, COMMENT) Review comments </skill_group>

<skill_group name="Commit Management"> List commits in a repository Show recent commits in lumelle Get details of a specific commit Get commit abc123def Commit message, author and committer, file changes, added/deleted lines, parent commits Compare two commits or branches Compare main and dev branches Files changed, diff stats, merge base </skill_group> </available_skills>

<best_practices> Write descriptive commit messages Link PRs to issues Use PR templates Review code before merging Delete merged branches Use labels for organization Protect main branch Push directly to main Create huge PRs Ignore review comments Forget to update documentation Leave stale issues open Use vague commit messages Skip code review </best_practices>

<error_handling> Authentication failed Verify GitHub token is set Check token has required scopes Regenerate token if expired Repository not found Verify repository name Check you have access Ensure correct owner/name format PR cannot be merged Check for merge conflicts Verify branch protection rules Ensure all reviews approved Rate limit exceeded Wait before retrying Use pagination Cache results </error_handling>

<output_format> Repository Information name: Repository name description: Repository description stars: Number of stars forks: Number of forks default_branch: Main branch name language: Primary language Pull Request number: PR number title: PR title state: open/closed/merged head: Head branch base: Base branch mergeable: Can be merged review_status: Review state </output_format>

<integration_notes> GitHub API rate limits: Authenticated requests: 5,000 per hour, Search API: 30 requests per minute. Claude will handle rate limiting automatically. Requires GitHub Personal Access Token with scopes: repo (full repository access), issues (issue management), pull_requests (PR management), workflows (GitHub Actions) Go to GitHub Settings → Developer settings → Personal access tokens → Generate new token (classic) </integration_notes>