MCP server/version-control

mcp-gitpro MCP Server

A context-efficient GitHub MCP server for AI agents.

vaur94/mcp-gitpro ↗by vaur94updated
Manual setup required. The maintainer's config contains paths only you know - edit the placeholders below before adding it to Claude Code.
1

Prepare the server locally

Run this once before adding it to Claude Code.

git clone https://github.com/vaur94/mcp-gitpro
cd mcp-gitpro

Then follow the repository README for any remaining dependency or build steps.

2

Register it in Claude Code

claude mcp add -e "MCP_GITPRO_GITHUB_TOKEN=${MCP_GITPRO_GITHUB_TOKEN}" mcp-gitpro -- node /absolute/path/to/mcp-gitpro/dist/index.js --config /absolute/path/to/mcp-gitpro/mcp-gitpro.config.json

Replace any placeholder paths in the command with the real path on your machine.

Required:MCP_GITPRO_GITHUB_TOKEN
3

Make your agent remember this setup

mcp-gitpro's config, env vars, and the gotchas you hit — recalled in every future Claude Code, Cursor, and Codex session. 

npx conare@latest

Free · one command · indexes the sessions already on disk. Set up in the browser instead →

What it does

  • GitHub-focused tool surface for repositories, issues, pull requests, search, and Actions
  • Read-only mode and toolset allowlists to reduce token waste
  • Built on the @vaur94/mcpbase package for reliable stdio communication
  • Comprehensive read and write coverage without requiring a local Git CLI

Tools 10

github_contextRetrieves current GitHub context information.
repository_readReads repository information.
repository_compareCompares repository branches or commits.
search_githubSearches across GitHub repositories.
issue_readReads details of a specific GitHub issue.
issue_writeCreates or updates a GitHub issue.
pull_request_readReads details of a specific pull request.
pull_request_writeCreates or updates a pull request.
actions_readReads GitHub Actions workflow information.
actions_writeTriggers or manages GitHub Actions workflows.

Environment Variables

MCP_GITPRO_GITHUB_TOKENrequiredGitHub personal access token for authentication

Try it

→List the open issues for the current repository.
→Search for repositories related to 'mcp-server' created by vaur94.
→Create a new issue titled 'Bug report' with the description 'Something is broken'.
→Get the status of the latest GitHub Actions workflow run.
→Compare the 'main' branch with the 'develop' branch in the current repository.
Original README from vaur94/mcp-gitpro

mcp-gitpro

🇬🇧 English | 🇹🇷 Turkce

✨ A production-ready, stdio-first GitHub MCP server built on @vaur94/mcpbase.

mcp-gitpro gives AI agents a compact GitHub tool surface without drifting into local git, filesystem mutation, shell execution, or browser automation. The goal is simple: high-value GitHub workflows, low context waste, and clear safety boundaries.

✨ Why mcp-gitpro

  • GitHub-focused tool surface for repositories, issues, pull requests, search, and Actions
  • Read-only mode, toolset allowlists, and exact-tool allowlists to reduce token waste
  • Strict TypeScript, stdio-first runtime, protocol tests, and release automation
  • Bilingual documentation with clearly separated English and Turkish doc trees
  • Built on the published @vaur94/mcpbase package instead of a local fork

📦 Installation

  • Node.js >=22.14.0
  • npm >=10
  • A GitHub token available as MCP_GITPRO_GITHUB_TOKEN

The setup below is for a local checkout of this repository.

Preferred repo-local setup:

bash ./scripts/install-local.sh

This installs dependencies, builds the server, and runs npm test once.

⚡ Quick Start

The commands below assume you are running from a clone of this repository, where scripts/install-local.sh and mcp-gitpro.config.json are available.

  1. Install and build once:
bash ./scripts/install-local.sh
  1. Launch the local stdio server:
export MCP_GITPRO_GITHUB_TOKEN=YOUR_GITHUB_TOKEN
node ./dist/index.js --config ./mcp-gitpro.config.json
  1. Optional pre-host verification:
npm run ci:check

Common host values:

  • launcher: node
  • entrypoint: /absolute/path/to/mcp-gitpro/dist/index.js
  • config flag: --config /absolute/path/to/mcp-gitpro/mcp-gitpro.config.json
  • token: MCP_GITPRO_GITHUB_TOKEN=...
  • protocol rule: stdout is reserved for MCP; logs belong on stderr

🔌 Integration Guides

Each guide follows the same pattern:

  1. run bash ./scripts/install-local.sh
  2. point the host to dist/index.js
  3. pass --config /absolute/path/to/mcp-gitpro/mcp-gitpro.config.json
  4. provide MCP_GITPRO_GITHUB_TOKEN
Host Integration model Guide
OpenCode opencode.json local MCP entry with command array OpenCode
Codex CLI / IDE config.toml with [mcp_servers.<name>] Codex
VS Code workspace MCP JSON with command, args, and env VS Code
Antigravity mcpServers JSON entry with absolute executable paths Antigravity

🧰 Tool Surface

Toolsets

  • context
  • repos
  • search
  • issues
  • pull_requests
  • actions

Tools

  • github_context
  • repository_read
  • repository_compare
  • search_github
  • issue_read
  • issue_write
  • pull_request_read
  • pull_request_write
  • actions_read
  • actions_write

⚙️ Configuration

Configuration precedence:

  1. built-in defaults
  2. mcp-gitpro.config.json
  3. MCP_GITPRO_* environment variables
  4. CLI flags handled by mcpbase

Important fields:

  • auth.githubToken
  • defaults.owner
  • defaults.repo
  • defaults.apiBaseUrl
  • context.readOnly
  • context.toolsets
  • context.tools
  • output.pageSize
  • output.maxFileLines
  • output.maxDiffLines
  • output.maxBodyChars

🏗️ Project Shape

mcp-gitpro/
|- src/
|  |- config/
|  |- core/
|  |- github/
|  |- shared/
|  |- tools/
|- tests/
|  |- unit/
|  |- protocol/
|- docs/
|  |- en/
|  |- tr/
|- scripts/

🔗 mcpbase Integration

  • mcp-gitpro depends on the published @vaur94/mcpbase package from npm
  • startup is wired with ApplicationRuntime, createMcpServer, and startStdioServer
  • config loading extends mcpbase through createRuntimeConfigSchema and loadConfig
  • execution context extends BaseToolExecutionContext with GitHubClient
  • streamable HTTP and telemetry remain intentionally unused in this GitHub-specific stdio product

📚 Documentation

🧪 Quality Gates

npm run build
npm run typecheck
npm run test
npm run test:coverage
npm r

Frequently Asked Questions

What are the key features of mcp-gitpro?

GitHub-focused tool surface for repositories, issues, pull requests, search, and Actions. Read-only mode and toolset allowlists to reduce token waste. Built on the @vaur94/mcpbase package for reliable stdio communication. Comprehensive read and write coverage without requiring a local Git CLI.

What can I use mcp-gitpro for?

Automating issue tracking and management directly from an AI chat interface. Querying repository metadata and branch comparisons without local git overhead. Triggering and monitoring GitHub Actions workflows via natural language commands. Searching for code or repositories across GitHub to provide context to AI agents.

How do I install mcp-gitpro?

Install mcp-gitpro by running: bash ./scripts/install-local.sh

What MCP clients work with mcp-gitpro?

mcp-gitpro works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Conare · memory for coding agents

Turn this server into reusable context

Keep mcp-gitpro docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Set up free$npx conare@latest

Related MCP Servers

PR Review MCP Server
AI-assisted code review tool for developers/AQA engineers
version-control22 stars
Bitbucket Data Center
MCP server for Bitbucket Data Center to search code and manage pull requests.
version-control11 stars
Continuum
Git remembers what you changed. Continuum remembers why.
version-control6 stars
RepoCrunch
Analyze any public GitHub repository into structured JSON.
version-control5 stars
bbkt
A Bitbucket CLI and MCP server for managing workspaces and repositories.
version-control3 stars
CERN GitLab MCP Server
Connects LLMs to CERN GitLab for discovering HEP code and documentation.
version-control3 stars