
Git Mcp Server
Let your coding agent open issues, read repos, and manage GitHub or GitLab from chat without leaving the editor.
Overview
git-mcp-server is a MCP server for the Build phase that exposes GitHub and GitLab repository operations to your coding agent over MCP.
What is this MCP server?
- Single MCP server for both GitHub and GitLab via GIT_PROVIDER
- Personal access token auth with optional self-hosted GIT_API_URL
- GIT_READ_ONLY mode to block write operations for safer audits
- stdio transport via npm package @raytien/git-mcp-server v0.2.3
- Package version 0.2.3 on npm as @raytien/git-mcp-server
- Supports two providers: github and gitlab via GIT_PROVIDER
- Four documented environment variables including secret GIT_TOKEN
What problem does it solve?
Agents cannot see your real GitHub or GitLab state unless you paste links or run manual CLI steps for every question.
Who is it for?
Solo builders who live in GitHub or GitLab and want the agent to triage issues, check PRs, or draft release notes from live API data.
Skip if: Teams that need deep local git graph operations only on disk without remote API access, or who refuse to grant PAT scopes to an agent.
What do I get? / Deliverables
After you register the server with GIT_TOKEN and provider settings, your agent can query and optionally mutate repos and issues through standardized MCP tools.
- Agent-callable tools against your chosen Git provider
- Optional read-only guardrail for exploration and audits
- Support for self-hosted GitLab or custom API URLs
Recommended MCP Servers
Journey fit
Source-control and provider APIs are wired while you build and ship code, so the canonical shelf is Build → integrations. This MCP exposes GitHub/GitLab APIs to agents for repos, issues, and merges—not frontend or infra provisioning.
How it compares
Git host API MCP bridge, not a local git porcelain skill or hosted CI runner.
Common Questions / FAQ
Who is git-mcp-server for?
It is for indie developers and small teams using AI coding agents who want direct GitHub or GitLab access from the IDE chat.
When should I use git-mcp-server?
Use it when you are building or shipping and need the agent to read issues, repos, or merge requests—or controlled writes—without switching to the browser.
How do I add git-mcp-server to my agent?
Install @raytien/git-mcp-server from npm, add a stdio MCP entry in Claude Code or Cursor, and set GIT_PROVIDER, GIT_TOKEN, and optional GIT_API_URL and GIT_READ_ONLY.