GitHub Inside Claude Code

io.github.KirchlivePublished by GitHub account Kirchlivev0.9.6Updated Oct 24, 2026

Normalized GitHub-CLI bridge for Claude Code — 89 ops, 6 families incl. federation sources

The publisher's own server: Claude Platform Docs

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Bridges the GitHub CLI into Claude Code, exposing 89 operations across six families, including optional Brave and Tavily research sources.

What you can do
This local MCP server wraps the GitHub CLI so an assistant can run GitHub operations from Claude Code, described as 89 operations grouped into six families. It also offers federation research operations that query external search sources, specifically Brave Search and Tavily search and research. No individual tool names or parameters are documented in the supplied material.
When to use it
Worth adding when you want an assistant to work with GitHub through the GitHub CLI inside Claude Code, and optionally to pull in web research results from Brave or Tavily alongside that work. It is a desktop-only local process, so it suits a developer machine rather than a hosted or browser-based setup.
Requirements
Runs locally over stdio, installed from PyPI as github-inside-claude-code and launched with uvx, so a Python tooling environment with uv/uvx is needed. The GitHub CLI is implied by the description. Optional secrets: BRAVE_API_KEY for the Brave Search source and TAVILY_API_KEY for the Tavily search and research sources, each needed only if that operation is invoked. No authentication is declared.
Before you install
Two optional secrets are read from the environment: BRAVE_API_KEY and TAVILY_API_KEY. Research operations send queries to third-party search providers, so anything included in those queries leaves your machine. GitHub operations may write, change, or delete repository data depending on the underlying CLI commands, and the supplied material does not list the individual tools, so review them before use.

Installation

In SourceWeft

  1. Open GitHub Inside Claude Code in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.9.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Claude integrations