git-remote-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMOTE_URL | No | HTTP API endpoint for push workflows. Alias for remote_url. | |
| remote_url | No | HTTP API endpoint for push workflows. Also accepted as REMOTE_URL. | |
| GIT_JWT_AUTH | No | JWT token sent as Authorization: Bearer <token>. Alias for git_jwt_auth. | |
| git_jwt_auth | No | JWT token sent as Authorization: Bearer <token>. Also accepted as GIT_JWT_AUTH. | |
| REMOTE_URL_FILE | No | Local file containing the HTTP API endpoint. Alias for remote_url_file. | |
| remote_url_file | No | Local file containing the HTTP API endpoint. Also accepted as REMOTE_URL_FILE. | |
| REQUEST_TIMEOUT_MS | No | Request timeout, default 30000. | 30000 |
| USE_REMOTE_URL_FILE | No | Set to true, 1, yes, or on to read the URL from a file. Alias for use_remote_url_file. | |
| use_remote_url_file | No | Set to true, 1, yes, or on to read the URL from a file. Also accepted as USE_REMOTE_URL_FILE. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitC | Run an allowed local git subcommand. |
| git_pushA | Create a diff file and upload its path to the configured HTTP API instead of running git push. |
| git_push_new_branchC | Ask the configured HTTP API to push a new branch to a git remote. |
| git_statusB | Run git status on the local repository. |
| git_logB | Read recent commits from the local repository. |
| git_diffC | Read a git diff from the local repository. |
| git_showC | Show an object from the local repository. |
| git_branchC | List or inspect branches in the local repository. |
| git_addC | Add file contents to the index. |
| git_commitC | Create a commit from staged changes. |
| git_checkoutC | Switch branches or restore working tree files. |
| git_switchC | Switch branches. |
| git_restoreC | Restore working tree files. |
| git_resetC | Reset current HEAD or paths. |
| git_rmC | Remove files from the working tree and index. |
| git_mvC | Move or rename a file, directory, or symlink. |
| git_tagC | List, create, or delete tags. |
| git_stashC | Manage git stashes. |
| git_mergeB | Merge a commit or branch into the current branch. |
| git_rebaseC | Reapply commits on top of another base. |
| git_cherry_pickC | Apply changes introduced by existing commits. |
| git_revertC | Revert existing commits. |
| git_cleanC | Remove untracked files from the working tree. |
| git_blameB | Show revision and author information for a file. |
| git_grepC | Search tracked files. |
| git_ls_filesC | List tracked files and other index information. |
| git_configC | Read or write repository git configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
The generic `git` tool overlaps with nearly every specific git_* tool, so agents must guess whether to use the catch-all or a dedicated command. `git_checkout`, `git_switch`, and `git_restore` also have overlapping semantics, and `git_push` vs `git_push_new_branch` require careful reading to distinguish.
All tools use a consistent git_ prefix and snake_case naming, making the set highly predictable. The lone exception is the generic `git` tool, which lacks a subcommand suffix and slightly breaks the pattern.
27 tools is heavy for this domain, and many duplicate functionality already exposed by the generic `git` tool. The set feels bloated rather than well-scoped, with several niche subcommands included while other essential ones are missing.
For a server named git-remote-mcp, critical remote operations like fetch, pull, clone, and remote management are absent. Local coverage is broad, but the remote lifecycle is severely incomplete and will cause agent failures for common workflows.