GitHub Chat MCP
The GitHub Chat MCP server allows you to analyze and query GitHub repositories using AI.
Index a GitHub repository: You must first index a repository to analyze its codebase, which is a necessary first step.
Query a GitHub repository: Ask detailed questions about an indexed repository and receive AI-generated responses.
Multi-turn conversations: Supports conversation history for follow-up questions.
Repository analysis: Provides insights into tech stacks, architecture, and other aspects of a repository.
Enables analyzing and querying GitHub repositories, including indexing repository content and asking questions about code architecture and tech stack
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., "@GitHub Chat MCP Index the React repository and tell me about its architecture"
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.
GitHub Chat MCP
A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API. Official Site: https://github-chat.com
Installation
# Install with pip
pip install github-chat-mcp
# Or install with the newer uv package manager
uv install github-chat-mcpStart using it with Claude!
Example prompts:
"Use github-chat-mcp to analyze the React repository"
"Index the TypeScript repository with github-chat-mcp and ask about its architecture"
GitHub Chat MCP server
Related MCP server: MCP GitHub Reader
Setup Instructions
Before anything, ensure you have a GitHub Chat API key. This is required to use the service.
Install uv first.
MacOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | shWindows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"Setup with Cursor (Recommended)
In mcp.json:
{
"mcpServers": {
"github-chat": {
"command": "uvx",
"args": [
"github-chat-mcp"
]
}
}
}With above, no envs required since it's a freemium release.
Setup with Claude Desktop
# claude_desktop_config.json
# Can find location through:
# Hamburger Menu -> File -> Settings -> Developer -> Edit Config
# Must perform: brew install uv
{
"mcpServers": {
"github-chat": {
"command": "uvx",
"args": ["github-chat-mcp"],
"env": {
}
}
}
}Installing via Smithery
You can install GitHub Chat for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install github-chat-mcp --client claudeUsing GitHub Chat with Claude
Index a GitHub repository first: "Index the GitHub repository at https://github.com/username/repo"
Then ask questions about the repository: "What is the core tech stack used in this repository?"
Debugging
Run:
npx @modelcontextprotocol/inspector uvx github-chat-mcpLocal/Dev Setup Instructions
Clone repo
git clone https://github.com/yourusername/github-chat-mcp.git
Install dependencies
Install uv first.
MacOS/Linux:
curl -LsSf https://astral.sh/uv/install.sh | shWindows:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"Then install MCP server dependencies:
cd github-chat-mcp
# Create virtual environment and activate it
uv venv
source .venv/bin/activate # MacOS/Linux
# OR
.venv/Scripts/activate # Windows
# Install dependencies
uv syncSetup with Claude Desktop
Using MCP CLI SDK
# `pip install mcp[cli]` if you haven't
mcp install /ABSOLUTE/PATH/TO/PARENT/FOLDER/github-chat-mcp/src/github_chat_mcp/server.py -v "GITHUB_API_KEY=API_KEY_HERE"Manually
# claude_desktop_config.json
# Can find location through:
# Hamburger Menu -> File -> Settings -> Developer -> Edit Config
{
"mcpServers": {
"github-chat": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/github-chat-mcp",
"run",
"github-chat-mcp"
],
"env": {
}
}
}
}Using GitHub Chat with Claude
Index a GitHub repository first: "Index the GitHub repository at https://github.com/username/repo"
Then ask questions about the repository: "What is the core tech stack used in this repository?"
Debugging
Run:
# If mcp cli installed (`pip install mcp[cli]`)
mcp dev /ABSOLUTE/PATH/TO/PARENT/FOLDER/github-chat-mcp/src/github_chat_mcp/server.py
# If not
npx @modelcontextprotocol/inspector \
uv \
--directory /ABSOLUTE/PATH/TO/PARENT/FOLDER/github-chat-mcp \
run \
github-chat-mcpThen access MCP Inspector at http://localhost:5173. You may need to add your GitHub API key in the environment variables in the inspector under GITHUB_API_KEY.
Notes
Level of logging is adjustable through the
FASTMCP_LOG_LEVELenvironment variable (e.g.FASTMCP_LOG_LEVEL="ERROR")This MCP server provides two main tools:
Repository Indexing - Index and analyze a GitHub repository
Repository Querying - Ask questions about the indexed repository
Available Tools
2 toolsindex_repositoryA
Index a GitHub repository to analyze its codebase. This must be done before asking questions about the repository.
Inputs: repo_url (required).
query_repositoryB
Ask questions about a GitHub repository and receive detailed AI responses. The repository must be indexed first.
Inputs: repo_url (required), question (required), conversation_history.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: index_repository is for preparing the repository for analysis, while query_repository is for asking questions about the indexed repository. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (index_repository and query_repository), using the same naming convention and structure throughout the set.
With only 2 tools, the server feels too thin for its apparent purpose of GitHub repository analysis. It lacks essential operations like listing repositories, managing indexes, or handling errors, which limits functionality and could cause agent failures.
The tool surface is severely incomplete for GitHub repository analysis. It covers only indexing and querying, missing core operations such as repository discovery, index management, or error handling, leading to significant gaps in workflow coverage.
Maintenance
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseCqualityDmaintenanceAn MCP server that analyzes local or remote GitHub repositories, providing intelligent code context and structure to AI coding assistants.1013MIT
- AlicenseDqualityDmaintenanceA lightweight MCP server for bringing GitHub repositories into context for large language models, enabling repository analysis, file access, and search without local cloning.47 npm6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.497 npmISC
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables GitHub API operations such as managing repositories, issues, and pull requests through natural language.Apache 2.0