git-readonly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
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 |
|---|---|
| git_list_repositoriesA | List configured workspace folders and whether each is an available Git repository root. |
| git_register_repositoryC | Register a Git worktree under a configured repository root and return its repositoryId. |
| git_statusA | Show branch and working tree status. |
| git_logC | Read bounded commit history. |
| git_show_commitA | Show commit metadata, changed files, and optionally its patch. |
| git_diffB | Compare working tree, index, HEAD, or two revisions. |
| git_range_diffC | Compare two commit ranges. |
| git_blameA | Show line-level commit attribution for a file. |
| git_grepB | Search tracked content without invoking a shell. |
| git_list_refsB | List local branches, tags, and remote-tracking refs. |
| git_list_treeB | List files and directories at a revision. |
| git_read_fileA | Read a bounded file from a revision, the index, or the working tree. |
| git_compare_refsB | Resolve two refs and report merge base and ahead/behind counts. |
| git_list_remotesA | List configured remote names without exposing URLs. |
| git_list_remote_refsA | List refs from a configured anonymous public HTTPS remote. |
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 15 tools
Each tool targets a distinct read-only Git operation: history, diffs, blame, search, refs, file access, and remotes. Potentially similar tools like diff vs range_diff and log vs show_commit are clearly separated by their descriptions and expected usage.
All tool names follow the consistent git_ prefix with a verb_noun pattern in lowercase snake_case. Composite names like list_remote_refs and range_diff are predictable extensions of the established convention.
Fifteen tools is at the high end of the ideal range, but each tool covers a distinct capability needed for comprehensive read-only Git inspection. No tool feels redundant or ornamental.
The surface covers repository discovery, status, history, commit inspection, diffs, blame, search, refs, tree browsing, file reading, comparison, and remote inspection. For a read-only Git server, this is a complete and coherent feature set with no obvious dead ends.