Skip to main content
Glama
github-mcp-lite

github-mcp-lite

by benjimkh

github-mcp-lite

A small Model Context Protocol server for GitHub — nine tools, PAT auth, stdio transport.

The official github/github-mcp-server covers a lot of ground (60+ tools). Handy for org admin and security workflows, but heavy if you mostly read files, scan PRs, and file issues. GitHub's been nudging people toward smaller tool sets for that reason (changelog, notes on token use).

This repo is the opposite end: fixed scope, short tool list, easy to skim before you plug it into an MCP host.

Install

git clone https://github.com/benjimkh/github-mcp-lite.git
cd github-mcp-lite
python3 -m venv .venv
source .venv/bin/activate
pip install -e .

Run it:

export GITHUB_TOKEN=ghp_...
github-mcp-lite

MCP client config (stdio):

{
  "mcpServers": {
    "github-mcp-lite": {
      "command": "/absolute/path/to/github-mcp-lite/.venv/bin/github-mcp-lite",
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

See examples/mcp-client.json.

Related MCP server: MCP GitHub CrunchTools

Tools

Tool

What it does

get_repo

Metadata, default branch, visibility, star count

search_code

Code search (repo:owner/name queries work well)

get_file_contents

Read a file or list a directory at a ref

list_pull_requests

Open / closed / all PRs

get_pull_request

Single PR with merge state and diff stats

create_issue

Open a new issue

comment_on_issue

Comment on an issue or PR thread

list_issues

Issues only (PRs filtered out)

search_repositories

Repo search

No gists, notifications, or org settings — that's intentional.

Benchmark

Ballpark tool/schema footprint vs the official server:

python3 benchmark/measure_schema_size.py

Background: docs/context-budget-guide.md.

This repo vs official github-mcp-server

github-mcp-lite

official server

Few repos, everyday PR/issue work

Org admin, security, Dependabot

Short tool list you can read in a minute

Actions, Projects, Discussions, etc.

PAT + stdio

Copilot OAuth integration

License

MIT — see LICENSE. PRs welcome; see CONTRIBUTING.md.

Available Tools

9 tools
comment_on_issueC

Add a comment to an issue or pull request.

Inputs: owner (required), repo (required), number (required), body (required). Returns: result

create_issueC

Create an issue. labels is a comma-separated list.

Inputs: owner (required), repo (required), title (required), body, +1 more. Returns: result

get_file_contentsA

Read a file or list a directory. Optional ref (branch, tag, sha).

Inputs: owner (required), repo (required), path (required), ref. Returns: result

get_pull_requestA

Fetch one pull request with merge state and diff stats.

Inputs: owner (required), repo (required), number (required). Returns: result

get_repoC

Repository metadata: branch, visibility, stars, description.

Inputs: owner (required), repo (required). Returns: result

list_issuesB

List issues only. state is open, closed, or all.

Inputs: owner (required), repo (required), state, per_page. Returns: result

list_pull_requestsC

List pull requests. state is open, closed, or all.

Inputs: owner (required), repo (required), state, per_page. Returns: result

search_codeC

Search code. Example: repo:owner/name TODO.

Inputs: query (required), per_page. Returns: result

search_repositoriesC

Search repositories using GitHub query syntax.

Inputs: query (required), per_page. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: issues, pull requests, repos, files, and search. No overlap in functionality; e.g., list_issues vs list_pull_requests are clearly separated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_issue, get_repo, search_code), making it predictable for an agent.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a 'lite' GitHub MCP, covering essential operations without being bloated or too sparse.

    Completeness3/5

    The tool set covers read operations extensively (get, list, search) and create for issues, but lacks update/delete for issues and PR creation/update, which are notable gaps for common workflows.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      A production-ready MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and more via both MCP stdio and REST API.
      27
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A minimal MCP server that enables creating GitHub repositories, committing files, and publishing releases using just a personal access token, without Docker or local Git.
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.
      -