Developer toolsPublic source

GitHub MCP Server

Complete GitHub and local git integration for ADK-Rust Enterprise agents. Provides 38 MCP tools covering the full repository lifecycle — from create_repository through git_push to create_release.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Full lifecycle — create repos, clone, branch, commit, push, open PRs, review, merge, release.

Real GitHub API — all remote tools call the live GitHub REST API with your PAT.

Local git operations — clone, init, add, commit, push, tag, log via local git binary.

Governed writes — issue creation, PR reviews, merges, and repo deletion are write operations.

Registry-ready — ships with mcp-server.toml for ADK-Rust Enterprise onboarding.

Architecture

How GitHub MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

GitHub MCP Server

Validates the request and owns 38 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

GitHub MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask GitHub MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

16 named tools shown from 38 documented tools

search_repos

Search GitHub repositories by query

read only

get_repo

Get repository details including default branch, language, and stats

read only

list_branches

List branches for a repository

read only

get_file_contents

Get file contents from a repository (decoded from base64)

read only

search_code

Search code across GitHub repositories

read only

list_pull_requests

List pull requests for a repository

read only

get_pull_request

Get a specific pull request with merge status and stats

read only

get_pr_diff

Get the diff for a pull request

read only

create_review

Create a review on a pull request

external write

create_issue

Create a new issue in a repository

external write

update_issue

Update an existing issue (title, body, state, labels)

external write

create_pull_request

Create a new pull request

external write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

8 read only6 external write2 destructive

delete_repository is irreversible — requires explicit confirmation in production
PR reviews require appropriate repo permissions
merge_pull_request respects branch protection rules
git_push requires configured credentials on the local machine
All write operations are audit-logged when used with MCP Registry

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install adk-mcp-github

MCP client configuration

export GITHUB_TOKEN=ghp_xxxxxxxxxxxx

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring