Skip to main content
Glama
ERSONUMECH

Local Repo Automation MCP

by ERSONUMECH

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_ALLOWED_ROOTSYesAllowlist of directories that the server can access. Use semicolons to separate multiple paths on Windows.
MCP_DEPLOY_COMMANDNoCommand to run for deployments. If not set, deployment is disabled.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_repositoriesC

Find Git repositories below an allowed directory.

repository_statusA

Show the current branch, porcelain status, and recent commit for a repository.

repository_diffB

Read a repository diff without changing files.

commit_repositoryA

Stage selected files and create a Git commit. Requires explicit confirmation.

create_pull_requestA

Push the current branch and open a GitHub pull request using gh. Requires explicit confirmation.

deploy_repositoryB

Run the configured MCP_DEPLOY_COMMAND in a repository. Requires explicit confirmation.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

Six tools is well-scoped for a local repository automation server, covering inspection, committing, PR creation, and deployment without unnecessary bloat.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo issues