github_add_issue_labels
Add labels to an issue or pull request.
LABSCO SUMMARY
Write access across the whole repository surface, with the raw API behind a confirmation string.
The coverage is wide enough that most GitHub work never needs a browser — file commits, branch creation, PR review requests and merges are all here — and the two generic REST tools mean an uncovered endpoint is not a dead end, with the write one requiring an explicit confirmation before it fires. The detail worth planning around is the SHA rule: updating or deleting a file needs the current SHA, so a read always precedes a write. Lazy tool loading exists for a real reason — forty-odd schemas is a lot of context to hand a client that only needs to read a file.
What it is
A broad GitHub server covering repository exploration and the full issue and pull-request lifecycle, with write operations that commit directly rather than only reading.
What you get
- Repository metadata, directory listings, a file's decoded contents with the SHA needed to update it, the README found regardless of casing, and code search within a repository
- Repositories listed for a user or organization, searched globally, created, or forked
- Issues listed, opened in full, created, updated and commented on, with labels created, listed, added, replaced and removed
- Pull requests listed and opened with diff stats and merge status, created, updated, given reviewers and merged
- Commits listed with filters for path, author, branch and date, one commit read with its complete diff, and two refs compared with ahead/behind counts and file changes
- Branches listed with protection status, created from a resolved ref, and deleted
- Files created, updated or deleted by direct commit — updates and deletions requiring the current SHA
- Releases listed with notes and asset URLs, and new ones created; user and organization profiles read
- Two generic tools for anything not covered: an arbitrary REST GET, and an arbitrary REST write guarded behind an explicit confirmation string
- Optional lazy tool loading — groups listed, searched and loaded on demand, so the client is not handed every schema at startup
Requirements
A GitHub personal access token in GITHUB_TOKEN or GITHUB_PERSONAL_ACCESS_TOKEN — a classic token with repo for private repositories and write operations, public_repo for read-only public access, and read:user for profile lookups. Passing it as a command-line flag is possible but exposes it to anyone who can run ps on the machine. Run it with npx github-mcp-server-kosta over stdio, from the npm package github-mcp-server-kosta, currently 3.1.0. --transport http serves a single Streamable HTTP endpoint, bound to 127.0.0.1 by default; if you bind anywhere else, set --http-auth-token and consider the host and origin allowlists, with --http-require-auth-on-public-bind refusing startup otherwise. An idle timeout exits the process after a period without requests, adjustable through MCP_IDLE_TIMEOUT_MS with 0 disabling it. In lazy tool mode only the bootstrap tools and the preloaded groups are exposed, defaulting to core and search.
Setup effort
One command plus a key — npm install -g github-mcp-server-kosta, then supply credentials
USE CASES
01
Understanding a repository you have just been pointed at
Read the metadata and README, then list the contents at the paths that look relevant.
02
Making a small fix and opening it for review
Create a branch, commit the file change with its current SHA, open the pull request and request reviewers.
03
Reviewing what a branch actually changed
Compare it against the base branch, then open the individual commits with their diffs.
04
Triaging the issue backlog
List the open issues by label, read the ones that matter, and relabel or comment as you go.
05
Finding where something is implemented
Search code within the repository, then read the files the results point at.
06
Cutting a release
Check the previous releases for the tag pattern, then create the new one with its notes.
07
Reaching an endpoint the tool set does not cover
Call the REST API directly — reads go straight through, writes require the confirmation string.
44 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
github_add_labels
Add one or more labels to an issue or pull request without replacing existing labels.
github_compare
Compare two git refs (branches, tags, or commits) and return the diff. Shows ahead/behind counts, commit list, and file changes. Useful for reviewing changes between releases or branches.
github_create_branch
Create a new branch in a GitHub repository from an existing ref. Resolves the source ref to a commit SHA, then creates the branch. Use before github_create_or_update_file for safe changes on a separate branch.
github_create_issue
Create a new issue in a GitHub repository. Requires a title; optionally set body (Markdown), labels, assignees, and milestone. Returns the created issue number and URL. Requires "repo" token scope.
github_create_issue_comment
Add a comment to an existing issue or pull request. Body supports GitHub-flavored Markdown. Works for both issues and PRs (they share the same comment API). Returns the comment ID and URL.
github_create_label
Create a new label in a GitHub repository.
github_create_or_update_file
Create a new file or update an existing file in a GitHub repository via a direct commit. For updates, you MUST provide the current file SHA (get it from github_get_file_content). Content should be the full file text (not a diff). Creates a commit on the specified branch.
github_create_pull_request
Create a pull request in a repository.
github_create_release
Create a new release in a GitHub repository.
github_create_repo
Create a new GitHub repository under the authenticated account.
github_delete_branch
Delete a branch from a GitHub repository.
github_delete_file
Delete a file via the GitHub Contents API. Requires the current file SHA.
github_fork_repo
Fork an existing GitHub repository to the authenticated account or organization.
github_get_commit
Retrieve full details of a specific commit by SHA, including message, author, timestamp, parent SHAs, and the complete diff (files changed with patches). Use after github_list_commits to inspect a change.
github_get_file_content
Read the contents of a single file from a GitHub repository. Returns decoded UTF-8 text, the file SHA (needed for updates via github_create_or_update_file), size, and URL. Files over 1MB cannot be retrieved via this endpoint.
github_get_issue
Retrieve full details of a specific issue by number, including title, body (Markdown), state, labels, assignees, milestone, and comments count. Use after github_list_issues to get complete information.
github_get_pull
Retrieve full details of a specific pull request by number, including title, body, diff stats (additions/deletions/changed files), merge status, head/base branches, and review status.
github_get_readme
Fetch and decode the README file of a GitHub repository. Automatically finds README regardless of casing or extension. Returns decoded content for quick project understanding.
github_list_branches
List all branches in a GitHub repository. Returns branch names, commit SHAs, and protection status. Use to discover branches before switching refs in other tools.
github_list_commits
List commits in a GitHub repository with optional filtering by file path, author, branch, and date range. Returns SHAs, messages, authors, and timestamps. Useful for understanding recent changes or tracking file history.
github_list_contents
List files and directories at a given path in a GitHub repository. Returns names, types (file/dir/submodule), and sizes. Use to explore repository structure before reading specific files with github_get_file_content.
github_list_issues
List issues in a GitHub repository with optional filtering by state, labels, and assignee. Returns titles, numbers, states, and labels. Note: GitHub API includes pull requests as issues; filter by absence of pull_request field for true issues.
github_list_labels
List labels in a GitHub repository.
github_list_pulls
List pull requests in a GitHub repository with optional filtering by state, head branch, and base branch. Returns PR titles, numbers, states, authors, and branch info.
github_list_releases
List releases in a GitHub repository including names, tag names, publication dates, pre-release status, and release notes. Returns asset download URLs.
github_list_repos
List repositories for a specific GitHub user or organization. Returns names, descriptions, languages, and star counts. Use github_search_repos for global search or this tool when you know the owner.
github_merge_pull_request
Merge a pull request.
github_remove_issue_label
Remove a label from an issue or pull request.
github_remove_label
Remove a single label from an issue or pull request.
github_repo_info
Retrieve metadata for a GitHub repository including stars, forks, open issues count, default branch, visibility, and language breakdown. Use as a starting point to understand a repository before exploring its contents.
github_request_reviewers
Request reviewers for a pull request.
github_rest_get
Perform an arbitrary GET request against the GitHub REST API (path-based).
github_rest_mutate
Perform an arbitrary write request against the GitHub REST API (guarded by an explicit confirmation string).
github_search_code
Search for code matching a query within a specific GitHub repository. Returns file paths and text fragments. Supports GitHub qualifiers like language:, filename:, extension:, and path: in the query string.
github_search_issues
Search issues and pull requests using GitHub Search Issues API. Use query qualifiers like "repo:owner/repo is:issue is:pr".
github_search_repos
Search GitHub repositories globally by keyword, language, stars, or other qualifiers. Returns matching repository names, descriptions, and star counts. Supports qualifiers like "language:", "stars:>100", "topic:", "org:".
github_set_issue_labels
Replace all labels for an issue or pull request.
github_tool_catalog_search
Search available tool groups and tool names without loading full tool schemas.
github_tool_groups_list
List available tool groups and whether they are loaded.
github_tool_groups_load
Load one or more tool groups and notify the client that the tool list has changed.
github_update_issue
Update an issue (or pull request) via the Issues API (edit title/body/state/labels/assignees/milestone).
github_update_pull_request
Update a pull request (title/body/state/base).
github_user_info
Retrieve a GitHub user's public profile: name, bio, company, location, public repo count, followers, and account creation date. Works for user and organization accounts.
BEFORE YOU INSTALL
What to know first
Tools you get
44 tools when we connected. In --tool-mode lazy only bootstrap tools and preloaded groups load, and some clients will not refresh when more arrive. github_add_labels and github_remove_label are aliases; github_rest_mutate needs confirm: "CONFIRM_GITHUB_WRITE".
Requires
- npx on PATH
- GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 44 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g github-mcp-server-kostaMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github": {
"command": "npx",
"args": [
"github-mcp-server-kosta"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
