set-github-tokenLABSCO SUMMARY
One call gives a model the shape of a repository, which is usually what it needs before anything else.
Reading files one at a time is how an assistant burns a conversation on orientation; a nested tree plus the stars, language and last-updated date answers 'what am I looking at' in a single response. It maps and summarises only — there is no file reading, no issues, no pull requests. The token being set through a tool call rather than an environment variable is a real trade: convenient in a shared client, but it means the token passes through the conversation.
What it is
A small TypeScript server that takes a GitHub repository URL and returns its directory structure as nested JSON along with a summary of the repository.
What you get
- map-github-repo — the full file and directory structure of a repository, returned as nested JSON
- Summary information alongside it: description, stars, forks, primary language, and the created and last-updated dates
- set-github-token — the Personal Access Token supplied in conversation rather than baked into a config file
Requirements
A GitHub Personal Access Token with the repo scope — a classic token, per the repository's instructions. The token is set through a tool call at the start of a session; until you do, every other call returns an error telling you so. Node.js v18.0.0 or later.
Setup effort
One command plus a key — npx -y @smithery/cli install github-mapper-mcp-server --client claude, then supply credentials
USE CASES
01
Sizing up a repository someone just linked you
Get the structure and the summary in one call and decide whether it is worth cloning.
02
Giving a model the layout before asking it about the code
The tree comes back as JSON, so the follow-up questions can name real paths rather than guessing at them.
03
Checking whether a project is still maintained
Stars, forks and the last-updated date arrive with the structure, so the judgement call happens in the same breath.
2 tools
Listed in project docs. Your client may show a different list.
map-github-repoBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js
INSTALLATION
Connect your client
Server setup
Claude Desktop
TERMINAL
npx -y @smithery/cli install github-mapper-mcp-server --client claudeMCP Clients
Cline, Roo Cline
TERMINAL
git clone https://github.com/dazeb/MCP-Github-Mapper.git
cd MCP-Github-Mapper
npm install
npm run buildAdd this to the client's MCP settings, pointing at build/index.js inside your clone:
JSON
{
"mcpServers": {
"github-mapper": {
"command": "node",
"args": [
"<YOUR_CLONE_DIRECTORY>/MCP-Github-Mapper/build/index.js"
]
}
}
}
