Github Test 2 MCP Server

The GitHub MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that provides seamless integration

Local serverstdioGo

What is the Github Test 2 MCP server?

If you already use Github Test 2, the github test 2 mcp server is the piece that lets your assistant work with it directly. The GitHub MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with GitHub APIs, enabling advanced automation and interaction capabilities for developers.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Toolset — Description
  • repos — Repository-related tools (file operations, branches, commits)
  • issues — Issue-related tools (create, read, update, comment)
  • users — Anything relating to GitHub Users
  • pull_requests — Pull request operations (create, merge, review)
  • code_security — Code scanning alerts and security features
  • experiments — Experimental features (not considered stable)
  • Users — The Users tool exposed by this server
  • Issues — The Issues tool exposed by this server
  • Repositories — The Repositories tool exposed by this server
  • Notifications — The Notifications tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_HOST, TOOL_ADD_ISSUE_COMMENT_DESCRIPTION, TOOL_CREATE_BRANCH_DESCRIPTION, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  1. To run the server in a container, you will need to have Docker installed. 2. Once Docker is installed, you will also need to ensure Docker is running. The image is public; if you get errors on pull, you may have an expired token and need to docker logout ghcr.io. 3. Lastly you will need to [Create a GitHub Personal Access

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Github Test 2's toolset — Toolset, repos, issues and 8 more — is a fair guide to whether it matches your workflow. It is maintained by armor-ai-onboarding; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Github Test 2's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Github Test 2.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ToolsetDescription
reposRepository-related tools (file operations, branches, commits)
issuesIssue-related tools (create, read, update, comment)
usersAnything relating to GitHub Users
pull_requestsPull request operations (create, merge, review)
code_securityCode scanning alerts and security features
experimentsExperimental features (not considered stable)
UsersThe Users tool exposed by this server.
IssuesThe Issues tool exposed by this server.
RepositoriesThe Repositories tool exposed by this server.
NotificationsThe Notifications tool exposed by this server.

How to install the Github Test 2 MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  1. To run the server in a container, you will need to have Docker installed. 2. Once Docker is installed, you will also need to ensure Docker is running. The image is public; if you get errors on pull, you may have an expired token and need to docker logout ghcr.io. 3. Lastly you will need to [Create a GitHub Personal Access
VariableDescriptionRequired
GITHUB_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes
GITHUB_HOSTEndpoint or connection string the server talks to.Optional
TOOL_ADD_ISSUE_COMMENT_DESCRIPTIONConfiguration value read at startup.Optional
TOOL_CREATE_BRANCH_DESCRIPTIONConfiguration value read at startup.Optional
YOUR_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Github Test 2 to Toolset.
  • Use Github Test 2 to repos.
  • Use Github Test 2 to issues.

Frequently asked questions

It connects Github Test 2 to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (Toolset, repos, issues, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Github Test 2 directly.