GitLab-CICD-Agent

The GitLab-CICD-Agent MCP server provides a natural-language driven interface to automate GitLab CI/CD workflows. It leverages a multi-agent system to interpret user requests, generate the necessary CI/CD artifacts (such as .gitlab-ci.yml, Dockerfiles, and deployment manifests), and push changes to GitLab while opening merge requests. You interact with the system by describing your desired pipeline in plain language, and the Supervisor and sub-agents handle plan generation, code/artifact creation, validation, and integration with GitLab via the dedicated MCP Tool Server.

To get started, connect your GitLab account through the app, then issue commands like: “Set up CI to run tests on push and deploy to GKE when main is updated.” The planner agent will break down the task, the code agent will generate the necessary GitLab CI configuration and infrastructure files, and the test agent will validate them. The GitLab MCP Server will apply changes (open MR, trigger pipelines), and you can monitor progress from the UI or GitLab itself. You can ask the ChatAgent for explanations of what the pipeline is doing or why a build failed.

Prerequisites: Node.js and npm installed on your machine; access to a GitLab account; optional: Git for cloning and pushing to repositories.

1. Clone the repository

git clone https://github.com/your-org/agentic-cicd.git
cd agentic-cicd

2. Install dependencies for backend and (if applicable) frontend

# Install backend dependencies
cd backend
npm install

# If you also run the frontend locally
cd ../frontend
npm install

3. Create environment configuration

• Backend/.env (example placeholders)

GITLAB_CLIENT_ID=your_gitlab_client_id
GITLAB_CLIENT_SECRET=your_gitlab_client_secret
GITLAB_REDIRECT_URI=https://your-frontend-url.vercel.app/oauth/callback

SUPABASE_URL=your_supabase_url
SUPABASE_KEY=your_supabase_key

google_api_key=your_gemini_api_key
TAVUS_API_KEY=your_tavus_key

4. Run the MCP server (node-based)

# From repository root or where your server entrypoint resides
npm run build-helper-if-needed
# Start the MCP server (adjust path as needed)
node path/to/server.js

5. Optional: run frontend/backend locally if needed

# Frontend
cd frontend
npm run dev

# Backend
cd backend
npm run start

Environment variables listed in the mcp_config block should be provided securely in your deployment environment. Ensure GitLab OAuth scopes grant access to the repositories you intend to manage (API read/write, MR creation, pipeline triggering). The system generates artifacts like .gitlab-ci.yml and Dockerfiles; review them in a feature branch before opening MRs. If you encounter YAML syntax errors during validation, use the TestAgent to perform linting and a dry-run of GitLab CI if supported. Monitor pipeline status directly in GitLab or via the ChatAgent updates in the MCP UI. For large deployments, consider enabling observability and tracing in your MCP Tool Server for easier debugging.