MCP BugBot GitLab
Installation (via PyPI)
Install the MCP BugBot GitLab package from PyPI:
pip install mcp-bugbot-gitlab
If you use a virtual environment (recommended):
python3 -m venv .venv source .venv/bin/activate pip install mcp-bugbot-gitlab
Overview
MCP BugBot GitLab is a Python-based MCP server designed to automate and streamline AI-powered code review for GitLab Merge Requests (MRs). It enables Cursor AI to view code and MRs, facilitating AI-assisted code reviews, Jira cross-verification, and professional feedback.
Configuration
You can configure MCP BugBot GitLab using environment variables, either directly or via your Cursor MCP configuration.
Required:
GITLAB_URL: Your GitLab server URL (e.g.,https://gitlab.com)GITLAB_TOKEN: Your GitLab Personal Access Token
Optional:
GITLAB_SSL_NO_VERIFY: Set to1to disable SSL verification (for self-hosted GitLab)GITLAB_USER: The GitLab username (if needed for API calls)JIRA_SERVER_URL,JIRA_TOKEN,JIRA_PROJECT_KEY: For Jira integration/cross-verification
Using with Cursor AI
-
Register the MCP Server with Cursor
Add the following to your
~/.cursor/mcp.json:{ "mcpServers": { "gitlab-bugbot": { "command": "/path/to/your/python", "args": ["-m", "mcp_bugbot_gitlab.server"], "description": "GitLab BugBot MCP server using venv Python", "env": { "GITLAB_URL": "https://gitlab.example.com", "GITLAB_TOKEN": "your_gitlab_token", "GITLAB_SSL_NO_VERIFY": "1", "GITLAB_USER": "your_gitlab_username", "JIRA_SERVER_URL": "https://jira.example.com", "JIRA_TOKEN": "your_jira_token", "JIRA_PROJECT_KEY": "YOURPROJECT" } } } }
- Adjust the
"command"path to your Python interpreter (e.g., from a virtualenv). - Set all environment variables as needed for your environment.
- Adjust the
-
Start Cursor
- Open Cursor and ensure the MCP server is registered.
- GitLab BugBot tools will be available in the Cursor tool interface.
Running the Server Manually
You can also start the server directly (for development):
python -m mcp_bugbot_gitlab.server
Development
Install dependencies
pip install -r requirements.txt
Run tests
pytest
Release & PyPI Publishing
- Releases are published to PyPI via GitHub Actions using OIDC (trusted publishing).
- To publish a new version, push a tag like
v1.2.3to GitHub. - See
.github/workflows/pypi-publish.ymlfor details.
License
MIT
Metadata
Release files for mcp-bugbot-gitlab 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_bugbot_gitlab-0.1.1.tar.gz | 12.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_bugbot_gitlab-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.9 kB
Release files / mcp_bugbot_gitlab-0.1.1.tar.gz
| Download URL | mcp_bugbot_gitlab-0.1.1.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbe3f3b3734864bff79b3795af7d32847ffa609bbcf4ad37112de793c22f7fe8
|
|
BLAKE2b-256 checksum How to use checksums |
3052dfb3572f1eac1c778d5ae978cf9e7a7e6581ad84acac024902b40c630cac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2025.
Transparency logRelease files / mcp_bugbot_gitlab-0.1.1-py3-none-any.whl
| Download URL | mcp_bugbot_gitlab-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c20d56e0cb850109d53a3731736dafcf35a1062de960f0aa6147fb1135c8f0e4
|
|
BLAKE2b-256 checksum How to use checksums |
0685ddf65d7e260b9cdf57efffa626e6d9f349d4ab2e1266d3f9321bfb3d1b2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2025.
Transparency logSecurity for mcp-bugbot-gitlab 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_bugbot_gitlab-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.