ado-mcp-server

by dmedellin

404 downloads
Not rated
GitHub

Description

<!-- filepath: /workspaces/ado-mcp-server/README.md --> # ado-mcp-server A Model Context Protocol (MCP) server for Azure DevOps. ## Overview This project implements an MCP server intended for integration with Azure DevOps. The server is built using the…

About

<!-- filepath: /workspaces/ado-mcp-server/README.md --> # ado-mcp-server A Model Context Protocol (MCP) server for Azure DevOps. ## Overview This project implements an MCP server intended for integration with Azure DevOps. The server is built using the `@modelcontextprotocol/sdk` and allows extension through a modular…

Details

Author
dmedellin
Downloads
404
Categories
Other

- Full support for Azure DevOps WIT REST API endpoints
- Extensible architecture for registering project and work item tools
- Provides linkWorkItems and unlinkWorkItems tools with configurable link types
- Runs over STDIO for integration with other systems
- Built using the official @modelcontextprotocol/sdk and zod for validation

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name ado-mcp-server
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Clone the repository, install dependencies with npm install, and start the server with npm start. It runs over STDIO and can be integrated with MCP-compatible clients. Testing can be done using the MCP Inspector: npx @modelcontextprotocol/inspector. No additional configuration is required for basic usage.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "ado-mcp-server": {
            "ado-mcp-server": {
                "command": "npx",
                "args": [
                    "@modelcontextprotocol/inspector"
                ]
            }
        }
    }
}

McpServers

{
    "ado-mcp-server": {
        "command": "npx",
        "args": [
            "@modelcontextprotocol/inspector"
        ]
    }
}

ado-mcp-server

A Model Context Protocol (MCP) server for Azure DevOps.

Overview

This project implements an MCP server intended for integration with Azure DevOps. The server is built using the @modelcontextprotocol/sdk and allows extension through a modular tool registration system.

Features

- MCP server implementation using the official SDK
- Extensible architecture for registering project and work item tools
- Full support for Azure DevOps Work Item Tracking (WIT) REST API endpoints (create, get, update, delete, list, query, batch, revisions, comments, attachments, relations)
- Runs over STDIO for integration with other systems

Getting Started

Prerequisites

- Node.js (version 16+ recommended)
- npm

Installation

Clone the repository and install dependencies:

git clone https://github.com/dmedellin/ado-mcp-server.git
cd ado-mcp-server
npm install

Usage

Start the MCP server:

npm start

The server will run over STDIO and can be integrated with compatible clients.

Testing

You can test the server using the Model Context Protocol Inspector:

npx @modelcontextprotocol/inspector

Project Structure

- index.js - Entry point; initializes and runs the MCP server.
- features/ - Directory for registering project and work item tools.

Scripts

- npm start - Start the MCP server.
- npm test - (Currently not implemented.)

Configuration

No additional configuration is required for basic usage. You may extend functionality by adding new tools in the features directory.

Dependencies

- @modelcontextprotocol/sdk
- zod

License

ISC

---

This project is not affiliated with Microsoft or Azure DevOps.

Tools

- linkWorkItems — Link two Azure DevOps work items (e.g., parent-child, related, etc.).
- Input:
- sourceId (number/string): The ID of the source work item (e.g., the child in a parent-child link).
- targetId (number/string): The ID of the target work item (e.g., the parent in a parent-child link).
- linkType (string, optional): The type of link (default: System.LinkTypes.Hierarchy-Forward for parent-child).
- comment (string, optional): Optional comment for the link operation.
- Permissions: Requires permission to edit work items in the Azure DevOps project.
- Example:

    {
"sourceId": 123,
"targetId": 456,
"linkType": "System.LinkTypes.Hierarchy-Forward"
}

- unlinkWorkItems — Remove a link (e.g., parent-child, related) between two Azure DevOps work items.
- Input:
- sourceId (number/string): The ID of the source work item (the one holding the link).
- targetId (number/string): The ID of the target work item (the one being linked to).
- linkType (string, optional): The type of link to remove (default: System.LinkTypes.Hierarchy-Forward for parent-child).
- Permissions: Requires permission to edit work items in the Azure DevOps project.
- Example:

    {
"sourceId": 123,
"targetId": 456,
"linkType": "System.LinkTypes.Hierarchy-Forward"
}

- For more link types, see Azure DevOps documentation.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.