
GitHub Inside Claude Code
- Kirchlive/github-inside-claude-code
GitHub Inside Claude Code is an MCP server that exposes 89 normalized GitHub CLI operations to coding agents over stdio.
About
GitHub Inside Claude Code is a Model Context Protocol server that wraps the GitHub CLI into a consistent tool surface for AI coding agents. developers and small teams use it when they want PRs, issues, repos, and related gh actions available as structured MCP calls rather than brittle terminal one-liners. The catalog describes 89 operations across six families, including federation-backed research helpers when you need web context next to repository work. Install runs through PyPI with uvx launching gh-tool-use-mcp over stdio; GitHub authentication follows your normal gh login. Tavily and Brave keys are optional and only required if you call those research operations. It matters for shipping faster with agents because GitHub becomes a dependable integration layer across build, review, and light ops tasks without custom scripts for every workflow.
- 89 normalized GitHub-CLI operations grouped into 6 operation families
- stdio MCP package via uvx gh-tool-use-mcp (PyPI 0.9.6)
- Federation sources for research ops (Tavily and Brave) alongside gh workflows
- Optional TAVILY_API_KEY and BRAVE_API_KEY only when research tools are invoked
- Targets Claude Code as a first-class GitHub-inside-agent experience
GitHub Inside Claude Code by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env TAVILY_API_KEY=YOUR_TAVILY_API_KEY --env BRAVE_API_KEY=YOUR_BRAVE_API_KEY github-inside-claude-code -- uvx github-inside-claude-codeAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | github-inside-claude-code |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Repository | Kirchlive/github-inside-claude-code ↗ |
What it does
Wire Claude Code (or another MCP client) to GitHub through a single normalized bridge instead of ad-hoc shell gh snippets.
Who is it for?
Best when you're living in Claude Code and want PR/issue/repo automation without maintaining a custom GitHub MCP wrapper.
Skip if: Skip if you forbid gh CLI on developer machines or need GitHub App-only enterprise policies without CLI.
What you get
After you register the server, your agent can call typed GitHub operations (plus optional research federation) from the same MCP session you use to write code.
- MCP-accessible GitHub repo/PR/issue workflows from your agent
- Optional web research calls alongside gh context
- Consistent tool schemas across 89 documented operations
By the numbers
- 89 operations
- 6 operation families
- Server version 0.9.6
Recommended MCP Servers
How it compares
MCP GitHub-CLI bridge with 89 ops, not a single-purpose agent skill or raw terminal-only gh usage.
FAQ
Who is GitHub Inside Claude Code for?
Developers who use Claude Code or another MCP client and want structured GitHub CLI access from the agent.
When should I use GitHub Inside Claude Code?
Use it whenever your agent should open PRs, manage issues, inspect repos, or pair gh actions with optional Tavily/Brave research during a build or ship workflow.
How do I add GitHub Inside Claude Code to my agent?
Add the PyPI package with stdio transport and runtime uvx gh-tool-use-mcp per server.json, authenticate gh locally, and set Tavily/Brave keys only if you use those research tools.