Azure DevOps MCP Connector

This utility serves as an MCP endpoint, granting Claude Desktop or Cline environments the capability to invoke operations against the Azure DevOps ecosystem.

Essential Requirements

• A functioning Node.js runtime (version 20 LTS or newer is mandatory).
• npm package manager (bundled with Node.js).
• A compatible MCP client application.
• Active credentials for an Azure DevOps workspace, specifically Personal Access Tokens (PATs).

Deployment Procedures

Automated Setup via Smithery

For rapid deployment to Claude Desktop environments using the Smithery manager:

bash npx -y @smithery/cli install @RainyCodeWizard/azure-devops-mcp-server --client claude

Manual Source Code Installation

1. Clone the source repository:

bash git clone https://github.com/RainyCodeWizard/azure-devops-mcp-server.git cd azure-devops-mcp-server

1. Install requisite dependencies:

bash npm install

1. Compile the project assets:

bash npm run build

Note: The output artifacts located in the build/ directory are intentionally excluded from version control; compilation must be executed post-cloning.

Configuration Parameters

Step 1: Generating the Azure DevOps Personal Access Token (PAT)

1. Navigate to your Azure DevOps portal and authenticate.
2. Access the user settings menu (typically via the profile icon in the upper-right corner).
3. Select the security configuration section.
4. Initiate the creation of a 'New Token'.
5. Assign a descriptive label to the token and carefully select the necessary permission scopes:
   • Code (read, write): Required for operations involving source control branches and pull requests.
   • Work Items (read, write): Necessary for managing tasks, bugs, and stories.
   • Build (read, execute): Needed for interacting with pipeline execution.
   • Wiki (read, write): For documentation management.
   • Project and Team (read): For enumerating available projects and team contexts.
6. Securely copy the generated token string.

Step 2: Integrating Server Details into Client Configuration

Modify your client's MCP settings file (cline_mcp_settings.json for VSCode or claude_desktop_config.json for the desktop app) by updating the mcpServers block as follows:

{ "mcpServers": { "azure-devops": { "command": "node", "args": ["/absolute/path/to/azure-devops-server/build/index.js"], "env": { "AZURE_DEVOPS_ORG": "your-organization-name", "AZURE_DEVOPS_PAT": "your-generated-pat-token", "AZURE_DEVOPS_PROJECT_ID": "your-specific-project-identifier" }, "disabled": false, "autoApprove": [] } } }

Mandatory Replacements:

• /absolute/path/to/azure-devops-server: The fully qualified file system path where the repository was cloned.
• your-organization-name: The identifier for your Azure DevOps organization.
• your-specific-project-identifier: The unique GUID or name associated with the target project.
• your-generated-pat-token: The access key copied in Step 1.

Supported Functionality (Tool Set)

Item Management

• get_work_item: Retrieval of a specific work item based on its unique identifier.
• list_work_items: Execution of Work Item Query Language (WIQL) statements to retrieve subsets of items.
• create_work_item: Instantiation of new work items (e.g., Defect, Task, Feature).
• update_work_item: Modification of existing work item attributes.

Project Visualization

• get_boards: Enumeration of accessible Kanban/Scrum boards within the context project.

Source Control (Git)

• list_repositories: Fetches metadata for all Git repositories present in the project.
• Output includes: ID, nomenclature, baseline branch reference, size metrics, and access URLs.
• get_file: Accesses the raw content of a specified file within a repository.
• Parameters:
  • repositoryId: The identifier of the target repository.
  • path: The file's location relative to the repository root (e.g., "src/config.ts").
  • branch: The specific branch reference (defaulting to 'main').
  • version: An optional commit SHA for historical retrieval.
• Returns: File content payload alongside metadata (path, size, last commit ID, modification timestamp).
• compare_branches: Generates a commit log detailing divergences between two specified branches.
• Parameters:
  • repositoryId: Target repository ID.
  • sourceBranch: The starting branch name.
  • targetBranch: The ending branch name.
  • maxCommits: Limit on the quantity of commits returned (default 100).
  • historyMode: Defines commit inclusion rules:
  • simplified: Standard log output (default).
  • first-parent: Excludes secondary parents from merge commits.
  • full: Includes all commits, including merges.
  • full-simplify-merges: Includes all commits but cleans up merge noise.
  • includeDetails: Boolean flag to enrich results with file change summaries (default false).
• Returns: A sequence of commit objects detailing author, timestamp, message, and optionally, a summary of file modifications (additions/deletions/edits).

Automation (Pipelines)

• list_pipelines: Retrieves a catalog of defined build and release pipelines.
• trigger_pipeline: Initiates an on-demand execution of a specified pipeline.

Merging Workflows (Pull Requests)

• list_pull_requests: Retrieves active or closed pull requests.
• create_pull_request: Submits a new request for code integration.
• update_pull_request: Modifies an existing pull request's properties.
• get_pull_request: Fetches detailed information pertaining to a single PR.

Documentation (Wiki)

• get_wikis: Lists all available wiki containers.
• get_wiki_page: Fetches the content of a specific wiki document.
• create_wiki: Provisioning of a new wiki container.
• update_wiki_page: Creation or modification of content within an existing page.

Organization Overview

• list_projects: Returns an enumeration of all accessible Azure DevOps projects within the connected organization.

Connection Validation

1. Ensure the client application (Cline/VSCode) is restarted after configuration modifications.
2. Confirm the Azure DevOps service is registered in the client's operational capabilities list.
3. Execute the diagnostic utility to test connectivity:

bash npm run inspector

Troubleshooting Common Issues

1. Connection Failures:

   • Scrutinize the file path specified in your MCP client settings for absolute correctness.
   • Re-validate the supplied Azure DevOps access credentials (PAT).
   • Examine the client application's internal log output for initialization errors.

2. Authorization Errors:

   • Check the PAT's expiration date.
   • Confirm that all required operational scopes (listed in Step 1) are granted to the token.
   • Verify consistency between the configured organization name and project ID.

3. General Operation Faults:

   • Utilize the inspector tool for immediate health checks.
   • Review the server's console output for runtime exceptions.

Modification and Extension

1. Apply necessary modifications within the source files located in the src directory.
2. Use npm run watch for continuous compilation during active development.
3. Execute npm run build when preparing for deployment.
4. Validate changes using the integrated inspector: npm run inspector

Licensing

This project is distributed under the terms of the MIT License. Consult the dedicated LICENSE file for specifics.

WIKIPEDIA: Cloud computing is defined by ISO as "a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand." It is frequently abbreviated as "the cloud".

== Key Attributes == In 2011, the U.S. National Institute of Standards and Technology (NIST) delineated five 'essential characteristics' defining cloud systems. The NIST definitions are as follows:

On-demand self-service: Capability for a consumer to unilaterally provision computing resources (e.g., server capacity, storage) automatically, eliminating the need for human mediation from the service provider. Broad network access: Services must be accessible via standard protocols across a network, supporting diverse client platforms (mobile devices, workstations, etc.). Resource pooling: Computing assets are aggregated to support multiple end-users through a multi-tenant architecture, allowing dynamic allocation and reallocation based on fluctuating demand. Rapid elasticity: Resources can be provisioned or decommissioned swiftly, often automatically, enabling the system to scale out or in rapidly to match requirement fluctuations. From the user perspective, capacity often appears infinite. Measured service: Utilization of metering capabilities at appropriate abstraction layers (processing, bandwidth, storage) to automatically track, optimize, and report resource consumption, ensuring transparency for both provider and consumer. The International Organization for Standardization (ISO) has since updated and expanded upon this framework as of 2023.

== Historical Context ==

The conceptual roots of shared computing trace back to the 1960s with the introduction of time-sharing systems facilitated by Remote Job Entry (RJE). During this period, centralized mainframe operations required users to submit tasks to dedicated operators. This era focused heavily on optimizing infrastructure efficiency to maximize access for multiple users. The adoption of the 'cloud' metaphor for virtualized offerings emerged around 1994, initially utilized by General Magic concerning the domain accessible by their Telescript mobile agents. David Hoffman, a communications specialist at General Magic, is credited with adapting the term from its prior usage in telecommunications networking. The term 'cloud computing' gained significant traction in 1996 when Compaq Computer Corporation outlined strategic business plans centered on leveraging the internet for scalable utility computing.