Git MCP Server
Enables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.
README
Git MCP Server
A Model Context Protocol (MCP) server that gives AI assistants the ability to inspect local Git repositories and interact with the GitHub API — reading commit history, diffs, file contents, issues, comments, pull requests, and project boards — all from a single, modular TypeScript server.
Tools
The server exposes 10 tools across four categories.
Git
| Tool | Description |
|---|---|
get_git_status |
Returns all uncommitted changes in a local repository (equivalent to git status). |
get_git_log |
Retrieves recent commit history with hash, author, date, and message. Accepts a maxCount limit. |
get-git-diff |
Shows line-by-line file differences. Can be scoped to a specific file or limited to staged changes only. |
get_repo_structure |
Returns the full directory and file tree of a repository — useful for architectural overviews and documentation. |
File System
| Tool | Description |
|---|---|
read_local_file |
Reads the entire content of a small file at once. Ideal for source files and configs. |
read_local_file_chunk |
Reads a specific line range (startLine–endLine) from a large file, avoiding unnecessary context. |
GitHub Issues
| Tool | Description |
|---|---|
fetch_all_issues |
Fetches all issues (open and closed) from a remote GitHub repository. |
get_issue_comments |
Retrieves all comments on a specific issue by number, including author and timestamps. |
create_and_board_issue |
Creates a new issue with title, body, labels, assignees, and priority — then automatically adds it to the repository's GitHub Projects board. Handles multi-project repos by prompting for project selection. |
GitHub Pull Requests
| Tool | Description |
|---|---|
fetch_merged_prs |
Lists recent pull requests from a repository. Toggle between merged and open PRs with isMerged. Useful for generating changelogs and release notes. |
Architecture
The server follows a layered, modular design introduced in PR #1:
src/
├── index.ts # Server bootstrap — wires tools to the MCP server
├── config.ts # Centralised environment config (GITHUB_TOKEN, cache TTL)
├── services/
│ ├── github-rest.ts # GitHub REST API client
│ ├── github-graphql.ts # GitHub GraphQL client (used for Projects v2 boarding)
│ ├── cache.ts # In-memory project metadata cache (1 h TTL)
│ └── git-cmd.ts # Local Git CLI wrapper
├── tools/
│ ├── git.ts # Git operation tools
│ ├── filesystem.ts # File reading tools
│ ├── issues.ts # GitHub Issue tools
│ └── pulls.ts # GitHub Pull Request tools
├── types/
│ ├── github.ts # GitHub API response types
│ ├── cache.ts # Cache types
│ └── git.ts # Git operation types
└── utils/
└── helpers.ts # Shared utility functions
Requirements
- Node.js v18 or later
- GitHub Personal Access Token with
repoandprojectscopes
Installation
# Clone the repository
git clone https://github.com/EnesOzturk11/Git-MCP-Server.git
cd Git-MCP-Server
# Install dependencies
npm install
# Build
npm run build
Configuration
The server reads a single environment variable:
| Variable | Required | Description |
|---|---|---|
GITHUB_TOKEN |
Yes | Personal Access Token for GitHub API authentication |
Create a .env file in the project root or export the variable in your shell:
GITHUB_TOKEN=ghp_your_token_here
Usage with Claude Desktop
Add the server to your Claude Desktop configuration file (claude_desktop_config.json):
{
"mcpServers": {
"git-mcp-server": {
"command": "node",
"args": ["/absolute/path/to/Git-MCP-Server/build/index.js"],
"env": {
"GITHUB_TOKEN": "ghp_your_token_here"
}
}
}
}
Restart Claude Desktop — the 10 tools will become available immediately.
Tech Stack
| Layer | Technology |
|---|---|
| Language | TypeScript 5 |
| Runtime | Node.js (ESM) |
| Protocol | Model Context Protocol SDK ^1.26.0 |
| Validation | Zod ^4.3.6 |
| GitHub API | REST + GraphQL (Projects v2) |
| Environment | dotenv |
Contributing
Issues and pull requests are welcome. Please open an issue first to discuss any significant changes.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.