Magg MCP Server: Support GitHub Actions, Integrate Auto Testing, PyPI Publishing & Mirror Management

Magg

GitHub Actions workflow configuration for the Magg project, including automated testing, PyPI publishing, and Docker image management functions

Developer tools Version control #Automated testing #PyPI publishing #Docker management #Version control .Python

rating : 2 points

downloads : 4.6K

update time : 2025-07-23

Open Site

What is the MCP server?

The MCP server is an automated tool that helps developers conduct code testing, version publishing, and Docker image building on GitHub. It achieves continuous integration and delivery through the integration of GitHub Actions.

How to use the MCP server?

The MCP server automatically executes tasks through the GitHub Actions workflow, such as running tests, publishing new versions to PyPI, building and pushing Docker images, etc. Developers only need to submit code to trigger these processes.

Use cases

Suitable for software projects that require automated testing, version management, and containerized deployment, especially Python - based packages or services.

Main Features

Multi - version testing

Supports running tests on multiple Python versions (such as 3.12, 3.13) to ensure compatibility.

Automatic version publishing

Automatically calculates the version number when merging into the main branch and publishes it to PyPI without manually updating the version file.

Docker image building

Builds Docker images for different environments (such as development, testing, production) based on branches or version tags and pushes them to the GitHub Container Registry.

GPG signing

Performs GPG signing on all commits and tags to ensure code integrity and security.

Advantages

Automated testing, building, and publishing processes save time

Ensures code quality and version consistency

Supports multi - environment deployment and version management

Limitations

Depends on GitHub Actions and requires familiarity with CI/CD processes

Requires the configuration of GPG keys and API tokens, and the setup is relatively complex

The version numbering strategy may not meet the requirements of some projects

How to Use

Submit code

Push the code to the GitHub repository. Submissions on any branch will trigger the testing process.

Wait for the tests to complete

GitHub Actions will automatically run the tests to ensure code quality.

Merge into the main branch

If the tests pass, merge the code into the main branch to trigger the version publishing process.

View the results

You can view the status of testing and publishing on the GitHub Actions page.

Usage Examples

Test Python compatibility across multiple versions

During the development process, the MCP server will automatically run tests on different Python versions to ensure code compatibility.

Publish a new version to PyPI

After the code is merged into the main branch, the MCP server will automatically generate a version number containing the commit count and publish it to PyPI.

Build Docker images

When the code is pushed to the beta branch, the MCP server will build a Docker image for development and a production image after the tests pass.