Azure DevOps Multi-Organization

A multi-organization MCP server for Azure DevOps enabling organization-scoped actions and optimized context handling.
  • typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "nikydobrev-mcp-server-azure-devops-multi": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-server-azure-devops-multi/dist/index.js"
      ]
    }
  }
}

You deploy and run a specialized MCP server for Azure DevOps that supports multiple organizations in a single chat session, routing actions by organization and optimizing responses for contextual usage.

How to use

You connect an MCP client to the Azure DevOps Multi-Organization MCP Server to perform organization-scoped operations such as listing organizations, listing projects, managing pipelines, repositories, and pull requests. Every tool call includes an organization parameter so you can target the correct Azure DevOps instance without restarting the server. The server runs locally via stdio during development and can switch to HTTP/SSE transport when deployed in the cloud by providing a PORT value.

How to install

Prerequisites: ensure you have Node.js 18 or higher installed on your system.

Install and build the MCP server locally using the project’s standard flow.

npm install
npm run build

Additional setup and usage notes

The server can run in two transports: stdio for local usage with Claude Desktop or VS Code, and SSE/HTTP for cloud deployment. For local usage, you start the server with a standard Node command pointing to the compiled entry file.

node /absolute/path/to/mcp-server-azure-devops-multi/dist/index.js

Cloud deployment notes

When you set an environment variable PORT, the server switches to SSE transport and exposes HTTP endpoints suitable for cloud deployments.

Common deployment patterns include containerized execution using Docker or cloud container services.

Available tools

list_organizations

View all configured organizations in the server configuration file and verify which orgs are available for routing.

list_projects

List all projects within a specified organization to help you navigate the Azure DevOps structure.

pipelines_get_builds

Fetch recent builds with context-optimized formatting to reduce verbose outputs.

pipelines_get_build_definitions

Retrieve build definitions with concise fields suitable for fast reference.

pipelines_run_pipeline

Trigger a new pipeline run with parameters and variables scoped to the selected organization.

pipelines_get_run

Get detailed information for a specific pipeline run.

pipelines_list_runs

List pipeline runs with filters to locate relevant instances quickly.

pipelines_get_run_log

Obtain the log content for a pipeline run.

git_list_repositories

List all Git repositories in a given project within an organization.

git_get_pull_requests

Search and list pull requests with filtering options across repositories.

git_create_pull_request

Create a new pull request with title, description, and reviewers.

git_get_repository

Fetch details for a specific repository.

list_organizations

View all configured organizations in the config.json mapping.

list_projects

List all projects within a specific organization.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
Azure DevOps Multi-Organization MCP Server - nikydobrev/mcp-server-azure-devops-multi | VeilStrat