release

This MCP server exposes a set of tooling utilities to manage Tekton releases via MCP. The server runs as a standalone Go binary (release-mcp-server) and registers tools such as create-release-branches, configure-hack-repo, and create-release-plans. After starting the server, configure Cursor to point at the server URL (/mcp) and you’ll see the registered tools. You can invoke each tool with its required inputs (e.g., minor_version, patch_version, component names) to generate release branches, update the hack repository configuration, and produce release plans. The tools clone relevant repositories, perform versioned branch creation, update configuration YAMLs, and generate RP/RPA files as needed, pushing changes on a new branch when applicable.

Prerequisites:

• Git installed
• Go (Golang) toolchain installed
• Access to the internet to clone public repos

Install and run:

1. Build the MCP server git clone https://github.com/savitaashture/release-mcp-server cd release-mcp-server go build -o release-mcp-server ./cmd/release-mcp-server

2. Run the MCP server ./release-mcp-server

3. Set up Cursor configuration (example) { "mcpServers": { "release-mcp-server": { "url": "http://0.0.0.0:3000/mcp" } } }

4. Ensure environment variables for tooling are available when required

• GITLAB_USERNAME
• GITLAB_TOKEN

Note: The repository includes three main tools registered under the MCP server: create-release-branches, configure-hack-repo, and create-release-plans. Each tool requires specific inputs, which are described in the README of the repository.

Tips and considerations:

• Ensure you have network access to clone upstream repositories used by the tools.
• The environment variables GITLAB_USERNAME and GITLAB_TOKEN are required for authentication when interacting with GitLab-hosted resources.
• Tools create branches (e.g., release-vX.Y.Z) and push changes to a new branch; you may want to prep credentials or SSH keys for seamless pushing.
• When using configure-hack-repo, the tool preserves existing YAML structure and only updates necessary sections like the branches and component configurations.
• Review permissions for the repositories involved to avoid merge conflicts or access issues during automation.
• The server exposes /mcp endpoints; ensure your firewall allows access to the configured port (default 3000 as shown in logs).
• If you update the server binary, re-build and restart the MCP server to pick up changes.