Implement support for Azure DevOps classic release pipelines also known as multi-stage release definitions

[mrvinaykj]

Summary

Implement support for Azure DevOps classic release pipelines (also known as multi-stage release definitions). These pipelines use a separate host (vsrm.dev.azure.com) and a distinct REST API surface that is currently not covered by any existing tools. The addition enables agents and users to create releases, monitor stage progress, and manage pre-deployment approvals entirely through MCP — without falling back to raw PowerShell REST calls.

Tools

Develop the following tools with full parameter support, including optional ones:

list_release_definitions: List classic release pipeline definitions in a project.

Endpoint: GET https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/definitions?api-version=7.1

list_releases: List releases for a given release definition.

Endpoint: GET https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/releases?definitionId={definitionId}&api-version=7.1

get_release: Get full details of a specific release, including environment/stage statuses and artifact versions.

Endpoint: GET https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/releases/{releaseId}?api-version=7.1

create_release: Create a new classic release, optionally pinning specific artifact versions.

Endpoint: POST https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/releases?api-version=7.1

update_release_environment: Trigger or update a stage (environment) within a release — used to queue a deployment.

Endpoint: PATCH https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/releases/{releaseId}/environments/{environmentId}?api-version=7.1

get_release_approvals: List pending or completed pre/post-deployment approvals for a release.

Endpoint: GET https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/approvals?releaseId={releaseId}&api-version=7.1

update_release_approval: Approve or reject a pending pre/post-deployment approval gate.

Endpoint: PATCH https://vsrm.dev.azure.com/{organization}/{project}/_apis/release/approvals/{approvalId}?api-version=7.1

Rules

1. Adhere strictly to existing project standards and coding conventions.
2. Ensure each tool exposes all API parameters (required and optional).
3. Use the official Azure DevOps Node API to interact with the APIs — specifically the IReleaseApi interface (getReleaseApi()).
4. Note that classic release APIs are served from vsrm.dev.azure.com, not dev.azure.com — the connection URL must be adjusted accordingly when initialising the release API client.

Special treat

If you follow the rules, you'll get candy!