What is Zapgit

ZapGit is a tool designed to automate GitHub workflows by integrating with MCP servers and LlamaIndex, allowing users to manage and plan tasks such as creating and commenting on issues and pull requests in one centralized location.

Use cases

Use cases for ZapGit include automating the process of issue creation and management, facilitating pull request comments, and enhancing team productivity by reducing manual tasks associated with GitHub.

How to use

To use ZapGit, clone the repository from GitHub, navigate to the directory, and set it up using either Docker or source code. For Docker, modify the .env file with your Groq API key and launch the application using provided scripts.

Key features

Key features of ZapGit include task automation for GitHub flows, integration with Zapier for enhanced functionality, and a user-friendly interface for managing issues and pull requests.

Where to use

ZapGit is primarily used in software development environments where teams need to streamline their GitHub workflows and improve collaboration on projects.

ZapGit🐈

Automate Your GitHub Flows with MCP!

ZapGit is aimed at creating an all-in-one place for you to manage and plan tasks like creating and commenting issues and pull requests on GitHub, using Zapier MCP servers and LlamaIndex.

Install and launch🚀

The first step, common to both the Docker and the source code setup approaches, is to clone the repository and access it:

git clone https://github.com/AstraBert/zapgit.git
cd zapgit

Once there, you can choose one of the two following approaches:

Docker (recommended)🐋

Required: Docker and docker compose

• Add the groq_api_key variable in the .env.example file and modify the name of the file to .env. Get these keys:
  • On Groq Console

mv .env.example .env

• Launch the Docker application:

# If you are on Linux/macOS
bash start_services.sh
# If you are on Windows
.\start_services.ps1

• Or do it manually:

docker compose up -f compose.local.yaml redis -d
docker compose up -f compose.local.yaml zapbackend -d
docker compose up -f compose.local.yaml zapfrontend -d

You will see the application running on http://localhost:8501 and you will be able to use it. Depending on your connection and on your hardware, the set up might take some time (up to 15 mins to set up) - but this is only for the first time your run it!

Source code🗎

Required: Docker, docker compose and conda

• Add the groq_api_key variable in the .env.example file and modify the name of the file to .env. Get these keys:
  • On Groq Console

mv .env.example scripts/.env

• Set up the app using the dedicated script:

# For MacOs/Linux users
bash setup.sh
# For Windows users
.\setup.ps1

• Or you can do it manually, if you prefer:

docker compose up -f compose.local.yaml redis -d

conda env create -f environment.local.yml

conda activate zapgit

cd scripts/

uvicorn api:app --host 0.0.0.0 --port 8000

conda deactivate

• Now you can open another terminal and run:

conda activate zapgit
cd scripts/
streamlit run frontend.py
conda deactivate

You will see the application running on http://localhost:8501 and you will be able to use it.

How it works

Database services

• Redis is used for API rate limiting control

Workflow

The workflow is very simple:

• When you submit a request, the request gets routed to a template prompt, which is completed based on the request details (thanks to banks)
• The chosen prompt is passed on to an Agent, which connects to Zapier MCP servers and starts executing all the commands contained in your requests
• Once the agent is done, it returns to you a final response and its agentic process. You should now see the action (create comment/issue/PR) on GitHub, a message on Discord detailing the action and a reminder event planned on Calendar.

Contributing

Contributions are always welcome! Follow the contributions guidelines reported here.

License and rights of usage

The software is provided under MIT license.