GitHub MCP Lightweight

Provides lightweight access to GitHub issues and PRs with essential fields for bulk analysis.

javascript

0

GitHub Stars

javascript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "wipiano-github-mcp-lw": {
      "command": "npx",
      "args": [
        "-y",
        "@wipiano/github-mcp-lightweight"
      ],
      "env": {
        "GITHUB_TOKEN": "ghp_your_personal_access_token_here"
      }
    }
  }
}

You have a lightweight GitHub MCP server designed for bulk analysis of issues and pull requests. It returns only the essential fields to minimize response sizes, helping you scan large repositories efficiently while staying within GitHub’s rate limits.

How to use

You use this MCP server by connecting a compatible MCP client to either a local (stdio) server or a remote HTTP endpoint. The lightweight server focuses on core data: issue/PR identifiers, URLs, titles, bodies, and comment bodies. With this setup, you can quickly enumerate large sets of issues and PRs, then fetch just the information you need for bulk analysis, data migration, or analytics pipelines.

How to install

Prerequisites: Node.js and npm should be installed on your system.

# Install the lightweight MCP server globally
npm install -g @wipiano/github-mcp-lightweight

Configuration and usage notes

To run the MCP server, you need a GitHub Personal Access Token (PAT) with the appropriate scopes. Generate a token with repo or public_repo (for public repos) and read:org if you access organizations. Then configure your MCP client to connect to the server using one of the supported methods shown below.

# Example for a local stdio-based setup via a client integration
# First, ensure you have a token ready
# Provide the token in the environment as GITHUB_TOKEN when launching the MCP client

Security and token handling

Store your GitHub token securely in environment variables. Use the minimal required scopes for your use case and rotate tokens regularly. Isolate tokens by environment to prevent cross-environment leakage.

Rate limiting and performance

The server is aware of GitHub API rate limits and will surface clear errors when limits are reached. For large repositories, narrow queries with precise timestamps (since) to reduce API calls and improve throughput.

Troubleshooting

If the server cannot start, verify that GITHUB_TOKEN is set and has the required scopes. If authentication fails, regenerate the token and ensure it has access to the target repository. If you receive empty responses, confirm the repository is accessible and that the since parameter is not set to a future date.

Notes on data scope

This MCP server returns a minimal data subset to keep responses small: id, html_url, title, body, and comment bodies for issues and pull requests.

Available tools

list_repository_issues

List issues from a GitHub repository with minimal response size, including only essential fields and comments bodies.

list_repository_pull_requests

List pull requests from a GitHub repository with minimal response size, including only essential fields and comments bodies.