Github Second Brain

GitHub Second Brain

A set of tools that strategically extract only the key information from any codebases, so your AI actually has enough context to assist you.
Explore the docs »

View Demo · Report Bug · Request Feature

Project Launch

Why?

The Problem

Even senior developers struggle with large, unfamiliar, interconnected codebases and their dependencies. For AI, this is even a bigger problem because without enough context, AI can't help, and will hallucinate but with too much, it will exceed its capability (context window limits).

Solution

This project develops tools for targeted, on-demand data extraction from diverse raw code repositories. It aims to provide AI clients (LLMs) with concise, query-relevant context/data to enhance understanding of unfamiliar or multiple codebases. This effectively manages token limits problem while complementing other existing AI tools.

✨ Features

• 😎 Latest Documentation on ANY GitHub Project: Grant your AI assistant seamless access to the GitHub project's documentation and code. The built-in retrieval tools help the AI gets tree directory and specific file content without exceeding Context Window Limit!

• 🧠 No More Hallucinations: With Github Second Brain, your AI assistant can provide accurate and relevant answers to your questions.

• ✅ Open, Free, and Private: Github Second Brain is open-source and completely free to use. It doesn't collect personal information or store queries. You can even self-host it!

• Extracting and analyzing data from GitHub repositories.

Getting Started

⚙️ Prerequisites

Before you begin, ensure you have met the following requirements:

1. To run the server in a container, you will need to have Docker installed.
2. Once Docker is installed, you will also need to ensure Docker is running. The image is public; if you get errors on pull, you may need to docker logout ghcr.io.

🚀 Installation

Usage with Claude Desktop

1. In Claude Desktop, go to Settings > Developer > Edit Config
2. Replace the configuration with:

{
  "mcpServers": {
    "github-second-brain": {
      "command": "docker",
      "args": [
          "run",
          "-i",
          "--rm",
          "ghcr.io/baonguyen09/github-second-brain-mcp"
      ]
    }
  }
}

Usage with Cursor

Update your Cursor configuration file at ~/.cursor/mcp.json:

{
  "mcpServers": {
    "github-second-brain": {
      "command": "docker",
      "args": [
          "run",
          "-i",
          "--rm",
          "ghcr.io/baonguyen09/github-second-brain-mcp"
      ]
    }
  }
}

⚙ How It Works

Github Second Brain connects your AI assistant to GitHub repositories using the Model Context Protocol (MCP), a standard that lets AI tools request additional information from external sources. What happens when you use Github Second Brain:

1. You provide a docker image to your AI assistant that is used to build a local MCP server, exposing tools for fetching issue context, file content, directory tree, etc.
2. Prompt the AI assistant on documentation/code-related questions.
3. Your AI sends requests to the locally built MCP server to use its tools (with your approval).
4. Local server executes the AI's request and returns the requested data.
5. Your AI receives the information and generates a more accurate, grounded response without hallucinations.

🗺️ Roadmap

We are continuously working to improve GitHub Second Brain. Here are some of our planned features:

• Add a mcp tool to retrieve specific file content and tree directory
• Add a mcp tool to trieve github issues + pull request
• Change the current gitingest processing to async

For a more detailed view of our upcoming features and to suggest new ones, please see the open issues and our project board.

🤝 Contributing

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

Non-technical ways to contribute

• Give the project a star⭐!: This will help make the project better for you because it will increase the project reliability and visibility which attracts more contributor to improve this project.
• Create an Issue: If you find a bug or have an idea for a new feature, please create an issue on GitHub. This will help us track and prioritize your request.
• Spread the Word: If you like GitHub Second Brain, please share it with your friends, colleagues, and on social media. This will help us grow the community and make it even better.
• Use GitHub Second Brain: The best feedback comes from real-world usage! If you encounter any issues or have ideas for improvement, please let us know by creating an issue on GitHub or by reaching out to Bao: thienbao05@arizona.edu .

Technical ways to contribute

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes (git commit -m 'Add some AmazingFeature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

Please read our Contributing Guidelines for detailed instructions on how to contribute, our coding standards, and the pull request process. Also, please review our Code of Conduct to understand the community standards we uphold.

🛠️ Tools

Github Second Brain provides AI assistants with several valuable tools to help them access, understand, and query GitHub repositories.

get_processed_repo (deprecated soon)

• This tool gives AI the entire codebase ingested into one prompt-friendly text file. It works by ingesting the entire codebase with gitingest library and serving it directly. This gives the AI a good comprehensive look of what the project is about. However, this tool isn't recommended and will soon be disabled because it can easily overflow AI with data, exceeding its Context Window Limit.

• When it's useful: For small repos, and to ask any types of questions: overview of the repo, how to contribute, etc.

get_tree_directory

• This tool gives AI the full tree directory of the codebase in plaintext with indentation. Instead of loading all the documentation (which could be very large), it can use this to understand the overview of the repo, and then use other tools to retrieve relevant parts only.

• When it's useful: For questions about the structure of the repositories.

get_file_content

• This tool returns full content of any files visible in the tree directory in plaintext.

• When it's useful: For specific questions about particular features, functions, concepts within a project, or any technical details not coverted in the documentation.

get_issue_context

• This tool returns detailed context of any github issues including title, body, metadata, and all the comments within that issue.

• When it's useful: For questions related to a github issue and the context around it.

📝 License

This project is licensed under the Apache License 2.0.

🙏 Acknowledgments

We would like to thank the following individuals and projects for their contributions and inspiration:

• Gitingest for the underlying tool.
• GitMCP for reference and setting the standards.
• Official GitHub MCP Server
• All our amazing contributors!

Disclaimer

Github Second Brain is provided "as is" without warranty of any kind. While we strive to ensure the reliability and security of our service, we are not responsible for any damages or issues that may arise from its use. GitHub projects accessed through Github Second Brain are subject to their respective owners' terms and conditions. Github Second Brain is not affiliated with GitHub or any of the mentioned AI tools.