github-mcp
<.
Give it the scopes you actually need (`repo` for private repo access,
`workflow` if you want it triggering Actions). On startup the server
checks the token's scopes where the token type exposes them, and prints
a warning immediately if `repo` or `workflow` is missing, rather than
letting it surface later as a confusing 403 on first use.
3. Add it to your Claude Desktop config. Don't create a
`claude_desktop_config.json` yourself somewhere and expect Claude Desktop
to find it, that file has to be the one the app actually reads, and
creating a separate one won't work. Instead, open Claude Desktop, go to
Settings -> Developer -> Edit Config, and that opens the real config
file for you to edit:
```json
{
"mcpServers": {
"github": {
"command": "node",
"args": ["/absolute/path/to/github-mcp/dist/index.js"],
"env": {
"GITHUB_TOKEN": "your-token-here"
}
}
}
}
```
4. Restart Claude Desktop.
## Notes
- The token is read from an environment variable at runtime and is never
written to disk by this server. Don't commit a token or a `.env` file to
this repo.
- Built against the official `@modelcontextprotocol/sdk`, `@octokit/rest`,
and `zod` for argument validation.
## License
MIT, see [LICENSE](./LICENSE).
]]>TDQS
Scored across 26 tools
Each tool targets a distinct resource-action pair, such as list_repos vs get_repo vs create_repo. Even similar tools like get_issue and get_pull_request operate on different object types with clear descriptions.
All tools use snake_case with a consistent verb_noun pattern: list_* for listings, get_* for retrieval, create_* for creation, and delete_*/merge_*/trigger_* for actions. There are no mixed conventions or vague verbs.
With 26 tools, the server is larger than the typical 3-15 scope, but GitHub's broad API justifies this size. Every tool serves a distinct purpose with no redundancy, so the count feels appropriate for the domain.
The server covers core GitHub workflows: repository, branch, file, issue, pull request, workflow, search, and user operations. Minor gaps like updating or deleting repositories are missing, but agents can work around them using existing tools.