Adk MCP Github

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.

Architecture

Key Principles

• 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.

Tools (38)

GitHub API — Search & Discovery

GitHub API — Repositories

GitHub API — Files

GitHub API — Pull Requests

GitHub API — Branches & Commits

GitHub API — Issues

GitHub API — CI/Actions

GitHub API — Releases

Local Git Operations

Verified Output

Tested against live GitHub API:

> search_repositories("org:zavora-ai mcp")
  ✓ 10 repos found

> get_repository(owner: "zavora-ai", repo: "mcp-a2a")
  ✓ zavora-ai/mcp-a2a | branch: main | lang: Rust

> list_tags(owner: "zavora-ai", repo: "mcp-a2a")
  ✓ v1.1.0 (7b5acb11), v1.0.0 (48e124f1)

> get_file_contents(owner: "zavora-ai", repo: "mcp-a2a", path: "Cargo.toml")
  ✓ 1191 bytes | sha: 6dab006f

> create_issue(owner: "zavora-ai", repo: "mcp-registry", title: "[Test] Integration verified")
  ✓ #1 created → https://github.com/zavora-ai/mcp-registry/issues/1

> git_log(path: ".", count: 3)
  ✓ 98768c9 feat: GitHub MCP v1.1.0 — 24 tools, full PR lifecycle, verified

Installation

Build from source

git clone https://github.com/zavora-ai/adk-mcp-github
cd adk-mcp-github
cargo build --release

The binary is at target/release/adk-mcp-github.

Configuration

export GITHUB_TOKEN=ghp_xxxxxxxxxxxx

Required scopes: repo, read:org, workflow (for Actions tools).

Claude Desktop

{
  "mcpServers": {
    "github": {
      "command": "/path/to/adk-mcp-github",
      "env": { "GITHUB_TOKEN": "ghp_xxxx" }
    }
  }
}

Kiro

{
  "mcpServers": {
    "github": {
      "command": "/path/to/adk-mcp-github",
      "env": { "GITHUB_TOKEN": "ghp_xxxx" }
    }
  }
}

Cursor

{
  "mcpServers": {
    "github": {
      "command": "/path/to/adk-mcp-github",
      "env": { "GITHUB_TOKEN": "ghp_xxxx" }
    }
  }
}

Windsurf

{
  "mcpServers": {
    "github": {
      "command": "/path/to/adk-mcp-github",
      "env": { "GITHUB_TOKEN": "ghp_xxxx" }
    }
  }
}

Governance

• 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 Server Manifest

server_id = "mcp_github"
display_name = "GitHub MCP"
version = "1.4.0"
domain = "developer"
risk_level = "medium"
writes_allowed = "gated"
transports = ["stdio"]
governance_gates = ["repo_policy", "codeowners_check"]

Contributors

License

Apache-2.0 — see LICENSE for details.

Part of the ADK-Rust Enterprise MCP server ecosystem.

Registry Compliance

This server implements the ADK MCP SDK contract:

• HealthCheck — async health probe for registry monitoring
• mcp-server.toml — manifest declaring tools, risk classes, and credentials
• Structured tracing — RUST_LOG env-filter for observability

rmcp and MCP compatibility

This server is built with rmcp 3.1.2 and requires Rust 1.94.1 or newer. The rmcp 3 rollout retains legacy MCP initialization compatibility and targets MCP protocol revisions 2025-11-25 and 2026-07-28.

MCP 2026-07-28 rollout (P2 high-impact)

This server uses rmcp 3.1.2 and adk-mcp-sdk 0.2 with a minimum supported Rust version of 1.94.1. It accepts stateless MCP 2026 requests with per-request protocol, client identity, and capability metadata while retaining the legacy MCP 2025-11-25 initialize flow for ordinary tools.

• Tasks: get_workflow_run
• MRTR approvals: create_pull_request_review, create_issue, update_issue, list_releases, create_release_note, create_pull_request, merge_pull_request, add_pr_comment, create_branch, delete_branch, create_or_update_file, create_repository, delete_repository, create_release, git_add
• Discovery and routing: rmcp serves on-demand discovery and validates the per-request protocol envelope; HTTP deployments can route with Mcp-Method and Mcp-Name. The packaged binary currently uses stdio.
• Caching: tools/list returns a public ttlMs of 60,000 for MCP 2026; rmcp omits the cache fields for legacy clients.
• Deprecated extensions: this server does not add new Roots, Sampling, or dynamic client-registration dependencies.

Protected tools require MCP_REQUEST_STATE_KEY with at least 32 high-entropy bytes. All replicas must share that key so sealed approval state can resume on another instance. Approval state is bound to the client identity, tool, and arguments and expires after two minutes. Missing identity, invalid state, rejection, or legacy protocol use fails closed. Task records are process-local for the current stdio runtime; use a durable task store before deploying the server behind scale-to-zero HTTP infrastructure.