Local Repo Automation MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Local Repo Automation MCP Show me the git status of the current repository."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local Repo Automation MCP
An MCP server for inspecting local Git repositories and automating common delivery tasks through git and the GitHub CLI (gh): status, diffs, commits, pull requests, and deployments.
Setup
npm install
npm run buildSet an allowlist before starting the server. Use semicolons on Windows:
$env:MCP_ALLOWED_ROOTS = "E:\src;E:\work"
$env:MCP_DEPLOY_COMMAND = "npm run deploy"
npm startRelated MCP server: Git MCP Server
Tests and Docker
npm.cmd test
npm.cmd run typecheck
npm.cmd run build
docker build --tag local-repo-automation-mcp:latest .GitHub Actions runs all three Node checks and the Docker build on every push and pull request. Start Docker Desktop before running the image build locally.
The GitHub CLI must be installed and authenticated for pull request creation. Deployment is disabled unless MCP_DEPLOY_COMMAND is set. All mutating operations require confirm: true.
Add .vscode/mcp.json to a VS Code workspace and build this project before connecting the server.
Tools
list_repositories: list Git repositories below an allowed directory.repository_status: inspect branch and working-tree state.repository_diff: read unstaged or staged diffs.commit_repository: stage selected paths and create a commit.create_pull_request: push a branch and open a GitHub pull request withgh.deploy_repository: run the configured deployment command in a repository.
Available Tools
6 toolscommit_repositoryA
Stage selected files and create a Git commit. Requires explicit confirmation.
Inputs: paths (required), message (required), repositoryPath (required), confirm.
create_pull_requestA
Push the current branch and open a GitHub pull request using gh. Requires explicit confirmation.
Inputs: title (required), repositoryPath (required), base, body, +1 more.
deploy_repositoryB
Run the configured MCP_DEPLOY_COMMAND in a repository. Requires explicit confirmation.
Inputs: repositoryPath (required), confirm.
list_repositoriesC
Find Git repositories below an allowed directory.
Inputs: root (required), maxDepth.
repository_diffB
Read a repository diff without changing files.
Inputs: repositoryPath (required), staged.
repository_statusA
Show the current branch, porcelain status, and recent commit for a repository.
Inputs: repositoryPath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct action (diff, commit, PR, deploy, list, status), so there is little overlap. repository_diff and repository_status both inspect state but serve clearly different purposes: one shows changes, the other shows branch/status/history.
Most tools follow a verb_noun pattern (repository_diff, commit_repository, create_pull_request, deploy_repository, list_repositories, repository_status). The pattern is mostly consistent, though repository_status and repository_diff place the noun first while commit_repository and deploy_repository place the verb first.
Six tools is well-scoped for a local repository automation server, covering inspection, committing, PR creation, and deployment without unnecessary bloat.
The set covers the core local workflow: inspect status/diff, commit, push via PR, and deploy. Minor gaps exist such as no explicit branch creation/checkout or push-only tool, but the main lifecycle is covered.
Maintenance
Related MCP Connectors
Manage repositories, users, releases, and automate GitHub workflows
Access the GitHub API, enabling file operations, repository management, search functionality, and…
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.-
- AlicenseAqualityDmaintenanceEnables local git operations including commit, branch, push, pull, status, and sync with conventional commit enforcement and branch naming conventions.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables high-level GitHub workflows such as cloning, branching, committing, pushing, creating pull requests and issues, all verified step-by-step via git and gh CLI.MIT
- AlicenseBqualityDmaintenanceEnables 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.10138 npmISC