Skip to main content
Glama
nikydobrev

Azure DevOps Multi-Organization MCP Server

by nikydobrev

pipelines_get_build_changes

Retrieve code changes and commits associated with a specific Azure DevOps build to track modifications and understand what triggered the build.

Instructions

Gets the code changes (commits) associated with a build

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationYesThe name of the Azure DevOps organization
projectYesProject ID or name to get the build changes for
buildIdYesID of the build to get changes for
continuationTokenNoContinuation token for pagination
topNoNumber of changes to retrieve, defaults to 100
includeSourceChangeNoWhether to include source changes in the results, defaults to false

Implementation Reference

  • The async handler function that retrieves code changes (commits) for a build using the Azure DevOps Build API and returns them as a JSON-formatted text response.
    async ({ organization, project, buildId, continuationToken, top, includeSourceChange }) => { const connection = await connectionManager.getConnection(organization); const buildApi = await connection.getBuildApi(); const changes = await buildApi.getBuildChanges(project, buildId, continuationToken, top, includeSourceChange); return { content: [{ type: "text", text: JSON.stringify(changes, null, 2) }], }; } );
  • Zod schema defining the input parameters, including organization, project, buildId, and optional pagination and filtering options.
    { organization: z.string().describe("The name of the Azure DevOps organization"), project: z.string().describe("Project ID or name to get the build changes for"), buildId: z.number().describe("ID of the build to get changes for"), continuationToken: z.string().optional().describe("Continuation token for pagination"), top: z.number().default(100).describe("Number of changes to retrieve, defaults to 100"), includeSourceChange: z.boolean().optional().describe("Whether to include source changes in the results, defaults to false"), },
  • The server.tool() call that registers the 'pipelines_get_build_changes' tool, including its name, description, input schema, and handler function.
    server.tool( "pipelines_get_build_changes", "Gets the code changes (commits) associated with a build", { organization: z.string().describe("The name of the Azure DevOps organization"), project: z.string().describe("Project ID or name to get the build changes for"), buildId: z.number().describe("ID of the build to get changes for"), continuationToken: z.string().optional().describe("Continuation token for pagination"), top: z.number().default(100).describe("Number of changes to retrieve, defaults to 100"), includeSourceChange: z.boolean().optional().describe("Whether to include source changes in the results, defaults to false"), }, async ({ organization, project, buildId, continuationToken, top, includeSourceChange }) => { const connection = await connectionManager.getConnection(organization); const buildApi = await connection.getBuildApi(); const changes = await buildApi.getBuildChanges(project, buildId, continuationToken, top, includeSourceChange); return { content: [{ type: "text", text: JSON.stringify(changes, null, 2) }], }; } );

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikydobrev/mcp-server-azure-devops-multi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server