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.
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.
- 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
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.
One command plus a key — npx -y @smithery/cli install github-mapper-mcp-server --client claude, then supply credentials
