git_directory_structureLABSCO SUMMARY
Two calls, in the right order.
The shape is deliberate: get the tree first so the model can choose which files matter, then read only those. That is cheaper on context than dumping a repository into the conversation, and it works on any repository your machine's git can clone.
What it is
A small Node.js MCP server that reads public git repositories. It clones into a temporary directory keyed by a hash of the repository URL, so the same repository is only fetched once and later calls reuse it.
What you get
git_directory_structure— take a repository URL and return an ASCII tree of its layoutgit_read_important_files— take a repository URL and a list of file paths, and return each path mapped to its contents- Repository reuse between calls, so browsing the tree then reading five files does not clone five times
Requirements
No account and no key. Node.js 14.x or higher and git installed on the system. Clone the repository, npm install, and point the client's config at node /path/to/mcp-git-repo-browser/src/index.js. It runs on stdio. Package mcp-git-repo-browser at 0.1.0, MIT.
Setup effort
Build from source — git clone https://github.com/razorback16/mcp-git-repo-browser
USE CASES
01
Understanding a library before depending on it
Read the tree, pick the entry point and the types file, and read just those two.
02
Answering a question about someone else's code
Point the assistant at the repository URL rather than pasting files into the chat.
03
Comparing how two projects solve the same thing
Pull the equivalent file from each repository in the same session — the clones are cached, so revisiting either is cheap.
2 tools
Listed in project docs. Your client may show a different list.
git_read_important_filesBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation. Nothing is published to npm; clone and run from source.
Requires
- Node.js 14.x or higher
- Git installed on the system
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/razorback16/mcp-git-repo-browser
cd mcp-git-repo-browser
npm installMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"mcp-git-repo-browser": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_GIT_REPO_BROWSER>/src/index.js"
]
}
}
}<YOUR_PATH_TO_MCP_GIT_REPO_BROWSER> is the full path of your clone. The block runs src/index.js directly, so there is nothing to build after npm install.
