mcpField
G
Github_private

Github_private

Remote
pipeworx.ioVersion Control0Updated 3d ago

About Github_private

Github_private is an MCP server for authenticated access to private GitHub repositories and organization data via OAuth. It is for users who need repository details, issues, pull requests, memberships, and file contents alongside public GitHub access.

Key features

  1. 01List private repositories
  2. 02Retrieve repository details and access level
  3. 03List issues and pull requests
  4. 04View organization memberships and roles
  5. 05Read repository file contents

Use cases

  1. 01Review private repository metadata
  2. 02Inspect issues and pull requests
  3. 03Check organization membership and role
  4. 04Retrieve a file from a private repository

MCP support

Exposes authenticated GitHub repository and organization tools to MCP clients, including repository, issue, pull request, organization, and file queries. It runs locally over stdio or through the Pipeworx gateway; gateway access requires a connected account and Pipeworx key.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/github_private/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-github_private

GitHub Private MCP Pack — access private repos, org data via OAuth. Complements the existing public github pack with authenticated access.

Part of Pipeworx — an MCP gateway connecting AI agents to 1879+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
gh_list_reposList all your repositories including private ones. Returns repo names, URLs, descriptions, language, stars, and last update time.
gh_get_repoGet detailed info for a specific repository. Returns description, language, stars, forks, open issues, default branch, and access level.
gh_list_issuesList issues in a repository. Specify owner and repo name (e.g., owner='octocat', repo='Hello-World'). Returns titles, numbers, status, assignees, and labels.
gh_list_pullsList pull requests in a repository. Specify owner and repo name (e.g., owner='octocat', repo='Hello-World'). Returns titles, numbers, status, reviewers, and merge state.
gh_list_orgsList organizations you're a member of. Returns org names, URLs, and your role (owner, member, etc.).
gh_get_fileGet file contents from a repository. Specify owner, repo name, and file path (e.g., 'README.md'). Returns raw content and metadata.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "github_private": {
      "url": "https://gateway.pipeworx.io/github_private/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/github_private/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1879+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack runs against a connected github_private account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect github_private, then call POST https://gateway.pipeworx.io/v1/tools/gh_list_repos with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gh_list_repos. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "github_private": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-github_private"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-github_private

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Github_private data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.