Github Private logo

Github Private

Reads private GitHub repositories, organizations, issues, pull requests, and files through MCP.

Install Github Private

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "github-private": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-github_private"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 6 tools correctly (8d ago).

Overview

Github_private MCP server connects AI clients to GitHub account data through OAuth, including private repositories and organization memberships. Its tools list repositories, issues, pull requests, organizations, repository details, and file contents. Use the hosted Pipeworx endpoint for gateway access or run the package locally over stdio when you do not want a gateway account. The server is suited to read-only repository research, project discovery, and code or issue context retrieval.

Use cases

  • List private repositories available to an account
  • Review open issues and pull requests in a repository
  • Inspect organization memberships and access roles
  • Read files from a private repository
  • Compare repository metadata across projects

Key features

  • Private repository discovery
  • Repository metadata lookup
  • Issue and pull request listing
  • Organization membership lookup
  • Repository file retrieval
  • Hosted OAuth and local stdio access

Tools6

What Github Private lets your agent do. Expand a tool for its parameters.

Verified live~599 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

What it can do

From the 6 tools this server returned when we ran it.

Read-only tools · 6
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age181 days
Maintainers1

Observed 2026-10-14 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-github_private (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads396Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Github Private works

What Github_private MCP server does

Github_private MCP server exposes read-focused GitHub tools through the Model Context Protocol. It can enumerate repositories available to the connected account, including private repositories, and return repository metadata such as descriptions, languages, stars, forks, open issue counts, default branches, and access levels.

The server also provides organization membership information, issue and pull request listings, and file retrieval. Issue results include titles, numbers, status, assignees, and labels. Pull request results include titles, numbers, status, reviewers, and merge state. File requests return raw content and metadata for a specified path.

These capabilities fit workflows that need repository context without opening GitHub manually, such as finding a project, reviewing open work, checking organization access, or reading a repository file.

How it works

The hosted deployment runs at the Pipeworx gateway and uses a connected github_private account. The gateway endpoint is https://gateway.pipeworx.io/github_private/mcp. A full Pipeworx gateway endpoint is also available; the pack endpoint lists this pack's tools directly and adds shared gateway meta-tools, while the local package exposes only the pack's own tools.

The pack's six primary tools are gh_list_repos, gh_get_repo, gh_list_issues, gh_list_pulls, gh_list_orgs, and gh_get_file. Repository-specific calls take an owner and repository name where applicable; file retrieval also takes a path.

Setup and configuration

For a hosted connection, sign in at Pipeworx, connect the github_private account, and add the MCP URL to a compatible client. The README provides configurations for Claude Desktop, Cursor, and Windsurf. HTTP clients can instead send requests to the gateway tools API with a Pipeworx key in the Authorization header.

Github_private MCP server also runs locally through the @pipeworx/mcp-github_private package. Configure an MCP client with npx -y @pipeworx/mcp-github_private as the command and no gateway account is required. The local process communicates over stdin and stdout.

Tools and capabilities

  • gh_list_repos: Lists accessible repositories, including private ones, with names, URLs, descriptions, languages, stars, and update times.
  • gh_get_repo: Returns detailed metadata for one repository.
  • gh_list_issues: Lists issues and their status, assignees, and labels.
  • gh_list_pulls: Lists pull requests, reviewers, and merge state.
  • gh_list_orgs: Lists organizations the account belongs to and the account's role.
  • gh_get_file: Reads a file from a repository and returns its content with metadata.

Limitations and notes

The documented pack tools read GitHub data; no write, merge, issue-creation, or file-editing tools are listed. Hosted connections include shared Pipeworx meta-tools in addition to the pack tools, so the tool count can exceed the six capabilities documented here. The local stdio package does not include those shared meta-tools or cross-catalog routing.

The exact hosted tool scope is reported by the connection's initialize response. Github_private MCP server requires a connected GitHub account for the hosted deployment, while the standalone package avoids the gateway account and round trip. Requests for issues, pull requests, or files must identify the relevant repository, and file retrieval requires a repository path.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Github Private

Github_private is an MCP server that connects AI clients to GitHub through OAuth and exposes tools for listing private repositories, repository details, issues, pull requests, organizations, and file contents. It runs through the Pipeworx gateway or locally with npx over stdio, depending on the connection method you choose.

Install it locally by configuring your MCP client to run `npx -y @pipeworx/mcp-github_private`. This uses stdin and stdout and does not require a Pipeworx account. For hosted access, add `https://gateway.pipeworx.io/github_private/mcp` and connect the GitHub account through Pipeworx.

Yes, Github_private works with Cursor. Add the hosted MCP URL to Cursor, or configure the local npx command as an MCP server.

Yes, Github_private can read file contents from accessible private repositories with `gh_get_file`. Provide the repository owner, repository name, and file path; the tool returns raw content and metadata.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGithub Private AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/github-private?style=directory)](https://allmcps.com/mcp/github-private)
HTML Embed
<a href="https://allmcps.com/mcp/github-private"><img src="https://allmcps.com/api/badge/github-private?style=directory" alt="Github Private on AllMCPs" /></a>