
Git Mcp Server
io.github.Ray0907Published by GitHub account Ray0907v0.2.3Updated Oct 24, 2026
MCP server for GitLab and GitHub
Overview
Local MCP server that lets an assistant read and modify GitHub or GitLab repositories, issues, merge requests, CI pipelines and comments.
- What you can do
- Read and search repository content: file contents, directory trees, branches, commit history and code search
- Write to repositories: push file changes in one commit and create branches
- Read, list, create and update issues
- Read, list, create, diff and merge pull/merge requests
- Inspect CI/CD pipelines and workflow runs, list jobs and fetch job logs
- Add and list comments on issues and merge requests, and look up the authenticated user
- When to use it
- Useful when you want an assistant to work directly with a GitHub or GitLab project from the desktop client: reviewing code and merge requests, triaging issues, checking pipeline status or committing small file changes without leaving the chat.
- Requirements
- Runs locally via npx from the npm package, so Node.js is needed. Requires a personal access token in GIT_TOKEN (GitHub scopes repo, read:org, workflow; GitLab scopes api, read_api, read_repository, write_repository). GIT_PROVIDER selects github or gitlab (default gitlab); GIT_API_URL points at self-hosted or Enterprise instances. Network access to the provider API.
Installation
In SourceWeft
- Open Git Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Git MCP Server
A clean, modular Git MCP server supporting both GitHub and GitLab.
Quick Start
Claude Desktop Configuration
Add to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
GitHub
GitHub Enterprise
GitLab.com (SaaS)
Self-Hosted GitLab
Read-Only Mode
Get Your Token
GitHub
- Go to GitHub > Settings > Developer settings > Personal access tokens > Tokens (classic)
- Generate new token with scopes:
repo,read:org,workflow - Copy the token (starts with
ghp_)
GitLab
- Go to GitLab > Settings > Access Tokens
- Create a new token with scopes:
api,read_api,read_repository,write_repository - Copy the token (starts with
glpat-)
Available Tools
Repository
Issues
Pull/Merge Requests
CI/CD (Pipelines / Workflow Runs)
Note: GitHub Actions workflow runs map to GitLab pipelines. The same tools work for both platforms.
Comments
Users
Configuration
Architecture
Development
Adding a New Tool
- Create file:
src/tools/{category}/{action}.ts
- Export from category index:
src/tools/{category}/index.ts - Add to allTools:
src/tools/index.ts
Inspired By
- gitlab-mcp - GitLab MCP server
- github-mcp-server - Official GitHub MCP server
License
MIT
Source: README.md at commit 8c0ae3a
Tools
0Version history
1- v0.2.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts