atelier-busco-github-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | GitHub Personal Access Token (for 5,000 req/hr and private repos) | |
| GITHUB_OWNER | No | Default GitHub user or organization name for queries | |
| GITHUB_TOKEN | No | GitHub Personal Access Token (for 5,000 req/hr and private repos) | |
| GITHUB_API_URL | No | Base URL for GitHub API (defaults to https://api.github.com) | https://api.github.com |
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 |
|---|---|
| list_repositoriesC | List repositories for a specified owner (user or organization), or the default GITHUB_OWNER. |
| get_repository_detailsA | Get comprehensive details, statistics, stars, forks, and settings for a specific GitHub repository. |
| list_branchesC | List branches for a given repository. |
| get_file_contentsA | Get decoded text content or raw metadata of a file in a GitHub repository. |
| list_directory_contentsB | List files, folders, symlinks and submodules within a directory in a GitHub repository. |
| get_repository_treeB | Get full or partial file structure tree for a repository, optionally recursive. |
| search_repositoriesB | Search for GitHub repositories using query syntax (e.g. topic, language, keywords). |
| search_codeB | Search for code across GitHub repositories or within a specific repository. |
| list_commitsC | List commit history for a repository or branch. |
| get_commit_detailsA | Get detailed information for a specific commit, including stats and modified file patches. |
| list_issues_and_prsC | List issues and pull requests in a repository. |
| get_issue_or_prA | Get details for a specific issue or pull request by its number. |
| list_releasesB | List published releases for a repository. |
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 13 tools
Each tool targets a distinct resource and action, such as retrieving a single repository versus listing all repositories versus searching repositories. Even the file-structure tools are clearly separated: file contents, directory listing, and repository tree serve different purposes.
All tool names follow a consistent verb_noun pattern using either get_, list_, or search_. The naming is predictable and clearly indicates both the operation and the resource being accessed.
With 13 tools, the server is well-scoped for a GitHub-focused MCP. Each tool covers a meaningful repository inspection or search operation without unnecessary bloat or redundancy.
The toolset covers the main read-oriented GitHub workflows: repository lookup, file browsing, code search, commits, releases, and issue/PR inspection. Minor gaps exist such as fetching tags, contributors, or PR comments, but they do not significantly hinder typical repository exploration tasks.