atelier-busco-github-mcp
OfficialProvides tools for interacting with GitHub repositories, enabling AI agents to inspect repositories, read file contents and trees, search code and repositories, and retrieve commits, issues, pull requests, and releases.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@atelier-busco-github-mcp show me the latest pull requests in the Atelier-Busco repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Atelier Busco GitHub MCP Server (atelier-busco-github-mcp)
A lightweight, robust Model Context Protocol (MCP) server built with Node.js and TypeScript to seamlessly connect LLMs and AI agents (Claude Desktop, Cursor, Antigravity, Cline) directly to GitHub repositories (public and private).
Key Features
Repository Inspection: List repositories for any user or organization, get repository metadata, statistics, and branch details.
File & Tree Exploration: Read and automatically decode file contents (base64 to UTF-8 text), browse directory trees, and fetch recursive Git trees.
Global & Local Search: Search repositories and code across GitHub or within specific repositories by language, file path, or query strings.
Git Tracking & History: Retrieve commit histories, detailed commit diffs/patches, issues, pull requests, and releases.
Hybrid Authentication Support:
Public Unauthenticated Mode: Out-of-the-box support without a token (standard GitHub rate limit: 60 requests/hour).
Authenticated Mode: Seamlessly activates when
GITHUB_TOKENorGH_TOKENis present (increases limit to 5,000 requests/hour and unlocks private repositories).
Related MCP server: GitHub MCP Server
Available MCP Tools
Tool Name | Description | Key Parameters |
| List repositories for an owner/organization or default |
|
| Retrieve comprehensive metadata and statistics for a repository |
|
| List branches for a given repository |
|
| Read and decode file contents in UTF-8 format |
|
| List files and subdirectories at a specific repository path |
|
| Get the full Git tree structure (supports recursive trees) |
|
| Search GitHub repositories using query qualifiers |
|
| Search for code snippets, symbols, or files |
|
| Fetch commit history for a repository or branch |
|
| Get commit details including modified files and patches |
|
| List issues and pull requests by status and labels |
|
| Retrieve details for a specific issue or PR by number |
|
| List published releases for a repository |
|
Environment Variables
Variable | Description | Required |
| Default GitHub user or organization name for queries | Optional (can be passed in tool calls) |
| GitHub Personal Access Token (for 5,000 req/hr and private repos) | Optional |
| Base URL for GitHub API (defaults to | Optional |
Client Configuration
1. Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"atelier-busco-github-mcp": {
"command": "node",
"args": [
"/path/to/atelier-busco-github-mcp/dist/index.js"
],
"env": {
"GITHUB_OWNER": "Atelier-Busco"
}
}
}
}Or running via tsx in development mode:
{
"mcpServers": {
"atelier-busco-github-mcp": {
"command": "npx",
"args": [
"tsx",
"/path/to/atelier-busco-github-mcp/src/index.ts"
],
"env": {
"GITHUB_OWNER": "Atelier-Busco"
}
}
}
}2. Antigravity (~/.gemini/config/mcp_config.json)
{
"mcpServers": {
"atelier-busco-github-mcp": {
"command": "node",
"args": [
"/path/to/atelier-busco-github-mcp/dist/index.js"
],
"env": {
"GITHUB_OWNER": "Atelier-Busco"
}
}
}
}Development & Build
# Install dependencies
npm install
# Build TypeScript to JavaScript
npm run build
# Start the compiled production server
npm run start
# Run with auto-reloading (development mode)
npm run devLicense
Available Tools
13 toolsget_commit_detailsA
Get detailed information for a specific commit, including stats and modified file patches.
Inputs: ref (required), repo (required), owner.
get_file_contentsA
Get decoded text content or raw metadata of a file in a GitHub repository.
Inputs: path (required), repo (required), ref, owner.
get_issue_or_prA
Get details for a specific issue or pull request by its number.
Inputs: repo (required), issue_number (required), owner.
get_repository_detailsA
Get comprehensive details, statistics, stars, forks, and settings for a specific GitHub repository.
Inputs: repo (required), owner.
get_repository_treeB
Get full or partial file structure tree for a repository, optionally recursive.
Inputs: repo (required), owner, tree_sha, recursive.
list_branchesC
List branches for a given repository.
Inputs: repo (required), page, owner, per_page, +1 more.
list_commitsC
List commit history for a repository or branch.
Inputs: repo (required), sha, page, path, +5 more.
list_directory_contentsB
List files, folders, symlinks and submodules within a directory in a GitHub repository.
Inputs: repo (required), ref, path, owner.
list_issues_and_prsC
List issues and pull requests in a repository.
Inputs: repo (required), page, sort, owner, +4 more.
list_releasesB
List published releases for a repository.
Inputs: repo (required), page, owner, per_page.
list_repositoriesC
List repositories for a specified owner (user or organization), or the default GITHUB_OWNER.
Inputs: page, sort, type, owner, +2 more.
search_codeB
Search for code across GitHub repositories or within a specific repository.
Inputs: query (required), page, path, repo, +3 more.
search_repositoriesB
Search for GitHub repositories using query syntax (e.g. topic, language, keywords).
Inputs: query (required), page, sort, order, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Access the GitHub API, enabling file operations, repository management, search functionality, and…
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables Large Language Models to analyze GitHub repositories in real-time, providing tools for retrieving repository information, analyzing issues, accessing documentation, and visualizing activity.-
- AlicenseAqualityNot gradedmaintenanceEnables AI agents to interact with GitHub repositories through the GitHub REST API for managing files, issues, and repository metadata. It supports both read operations like searching code and write operations such as creating repositories and updating issue comments.9-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repositories, including fetching repository details, searching, and retrieving README content.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with GitHub repositories, issues, pull requests, code, and more through a comprehensive set of tools.-