Github MCP Lw MCP Server

Lightweight GitHub MCP server optimized for efficient issue and pull request analysis

Local serverstdioGo

What is the Github MCP Lw MCP server?

If you want an AI assistant working directly with Github MCP Lw, the github mcp lw mcp server is the bridge. Lightweight GitHub MCP server optimized for efficient issue and pull request analysis.

What Github MCP Lw does

A lightweight GitHub MCP (Model Context Protocol) server optimized for efficient issue and pull request analysis. This server provides minimal response sizes by returning only essential fields, making it perfect for bulk analysis of GitHub repositories.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • list_repository_issues — List issues from a GitHub repository with minimal response size
  • list_repository_pull_requests — List pull requests from a GitHub repository with minimal response size

Installing the github mcp lw mcp server

The server is distributed via npm as @wipiano/github-mcp-lightweight, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: GITHUB_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Github MCP Lw sits in that group, and the shape of its toolset — list_repository_issues, list_repository_pull_requests — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by wipiano, written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the github mcp lw mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
list_repository_issuesList issues from a GitHub repository with minimal response size.
list_repository_pull_requestsList pull requests from a GitHub repository with minimal response size.

How to install the Github MCP Lw MCP server

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

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Github MCP Lw to list repository issues.
  • Use Github MCP Lw to list repository pull requests.

Frequently asked questions

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