mcp-github-integration

This MCP server bridges GitHub API capabilities into the MCP (Model Context Protocol) ecosystem via a TypeScript client library. It exposes 129 MCP tools that cover core GitHub operations such as repository management, issue tracking, pull requests, branches, commits, releases, content operations, GitHub Actions, webhooks, collaborators and teams, repository statistics, and security settings. The server is designed to be invoked through the MCPServer interface, taking a GitHub token for authentication, and then handling requests mapped to specific GitHub API methods. Use the provided handleRequest pattern to call methods like github_get_repository, github_create_issue, or github_list_pull_requests, specifying the appropriate params. This enables you to perform complex GitHub workflows from within your MCP-enabled environment with typed result data and standardized error handling.

Prerequisites:

• Node.js (LTS) and npm installed
• Git installed
• Access to the repository or npm registry to install the package

From NPM (recommended for quick start):

npm install @onamfc/mcp-github-integration

From Source:

git clone https://github.com/onamfc/mcp-github-integration.git
cd mcp-github-integration
npm install
npm run build

Run locally after installation/build:

# Ensure you have a GitHub token with appropriate scopes
export GITHUB_TOKEN=your_github_token_here

# Start the server (path may vary after build; adjust as needed)
node dist/server.js

Configure your MCP client to connect to this server according to your MCP setup.

Environment variables and configuration:

• GITHUB_TOKEN is required for authentication with the GitHub API. Set it in your environment before starting the server.
• When building from source, ensure the build artifacts are emitted to dist/ and that dist/server.js is the entry point used by the MCP runner.
• If you upgrade the package, verify the 129 MCP tool names and their parameter schemas, as GitHub API endpoints can change or deprecate over time.
• Use the built-in logging via @onamfc/developer-log and inspect package metadata with @onamfc/pkg-inspect for troubleshooting.
• For local development, consider providing a local mock GitHub server or using a dedicated test repository to avoid impacting production data.