mcp-repo-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_REPO_TOOLS_TOKEN | No | If set, HTTP requests must send "Authorization: Bearer <token>" |
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 |
|---|---|
| read_fileA | Read a text file from the repository, optionally a line range, either from the working tree or at a specific commit ( |
| search_codeA | Search tracked files for a string or regex (git grep). Searches the working tree by default, or a specific commit with |
| list_changed_filesA | List files changed between two commits, with status, line counts, and whether each file is a test (by the server's test globs). Cheap; call this before get_diff to decide what to read. Paths of changed files are always listed, even ones whose contents the path policy hides. |
| get_diffA | Get the unified diff between two commits, split per file. Defaults to pull-request semantics (changes on head since it branched from base). Output is capped: files that don't fit have |
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 4 tools
Each tool has a fairly distinct role: read_file (single file contents), search_code (grep across tracked files), list_changed_files (cheap change summary), and get_diff (full unified diff). The only mild overlap is between list_changed_files and get_diff, but the descriptions explicitly position them as a cheap-then-expensive pair, so an agent can tell them apart.
All four tools follow a clean verb_noun snake_case pattern: read_file, search_code, list_changed_files, get_diff. Verb style is consistent and the convention is predictable across the set.
Four tools is a reasonable, tightly-scoped set for read-only repository inspection. It is on the lean side but each tool earns its place with no redundancy, so it is not thin enough to penalize heavily.
The read/find/diff lifecycle is covered, but there is no way to enumerate the directory tree, list commits/branches, or view history/blame, which limits discovery of what to inspect. An agent can partly work around file discovery via search_code, but the lack of commit enumeration is a notable gap for a git-oriented surface.