mcp-server-github
Provides tools for interacting with GitHub repositories, issues, pull requests, and other GitHub data via the GitHub API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-githubshow open issues in my repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-github
GitHub operations MCP server
Quick Start
cd mcp-server-github
npm install
kadi install
kadi run build
kadi run startNote: The runtime entrypoint is dist/index.js (package.json start: "node dist/index.js"), so ensure you run the build step before starting.
Related MCP server: Git PR MCP Server
Configuration
agent.json
Field | Value |
Name | mcp-server-github |
Version | 0.1.0 |
Start script | node dist/index.js |
Build (default) | from: node:20-alpine, cli: latest |
Build run steps | npm install -g bun; npm ci --include=dev; bun build ./src/index.ts --outdir ./dist --target node --external pino --external pino-pretty --external @octokit/rest; npm prune --omit=dev |
Build env | NODE_ENV=production |
Runtime / Environment notes
Transport mode: The server checks MCP_TRANSPORT_TYPE (case-insensitive). If unset or set to "stdio", the server runs in STDIO mode and ANSI colors are disabled (NO_COLOR=1, FORCE_COLOR=0).
Startup logs include:
server name and version (config.mcpServerName / config.mcpServerVersion),
selected transport (config.mcpTransportType),
GitHub API host (config.githubHost or config.githubApiUrl),
GitHub token presence (masked in logs, showing only the last 4 characters if set).
On startup the application composes the dependency-injection container (composeContainer) and creates the MCP server instance (createMcpServerInstance).
The selected transport is started via startTransport(server, createMcpServerInstance). For HTTP transport a factory (createMcpServerInstance) is provided so each session gets a fresh server instance.
In STDIO mode, fatal startup errors are written directly to stderr; otherwise they are logged via the logger.
The server installs handlers for SIGTERM and SIGINT to log shutdown and exit gracefully (process.exit(0)). Uncaught exceptions are logged (including stack) and the process exits with code 1.
The server uses the compiled output in dist/ (built by the kadi build process defined above).
Development
npm install
kadi install
kadi run build
kadi run startNotes:
The build uses bun to compile TypeScript (src/index.ts) to dist/.
The start script runs the compiled Node server (node dist/index.js).
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/a-g-e-n-t-s/mcp-server-github'
If you have feedback or need assistance with the MCP directory API, please join our Discord server