mcp-server-github
An MCP server that enables GitHub API operations such as managing repositories, issues, and pull requests through natural language.
README
mcp-server-github
GitHub operations MCP server
Quick Start
cd mcp-server-github
npm install
kadi install
kadi run build
kadi run start
Note: The runtime entrypoint is dist/index.js (package.json start: "node dist/index.js"), so ensure you run the build step before starting.
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 start
Notes:
- The build uses bun to compile TypeScript (src/index.ts) to dist/.
- The start script runs the compiled Node server (node dist/index.js).
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.