v0.0.1

This release introduces the first functional .NET-based Azure DevOps Server MCP fork focused on on-prem scenarios. It delivers a practical MCP toolset for work item and repository workflows, adds the configuration model needed for Azure DevOps Server collections, and provides a reusable ASP.NET Core integration package for embedding these tools into other MCP hosts.

Highlights

Introduces a .NET MCP implementation for Azure DevOps Server / on-prem use cases
Adds end-to-end work item and repository workflow support
Supports multi-collection access through per-request collection parameters and collection-specific PAT headers
Provides a reusable ASP.NET Core integration package alongside the standalone server

Available MCP Tools

This release makes the following on-prem Azure DevOps MCP tools available:

wit_get_work_item to retrieve a work item with core fields and full comment context
wit_work_item_write_create to create a new work item with type, title, and optional description
wit_add_work_item_comment to add a comment to an existing work item
wit_update_work_item_comment to update an existing work item comment
repo_create_branch to create a feature branch from an existing branch
wit_add_artifact_link to link a branch to a work item as an artifact relationship
repo_create_pull_request to create a pull request and link it to the related work item

Functional Scope

The main outcome of v0.0.1 is a practical work-item-driven delivery flow for Azure DevOps Server:

retrieve the current context of a work item, including comments
create a new work item when needed
add or update work item comments from MCP
create a feature branch for implementation
link that branch back to the work item
open a pull request already connected to the tracked work

This release also improves comment handling to align with Azure DevOps rich text comment behavior and supports optional Markdown descriptions when creating pull requests.

Configuration and Runtime Notes

Azure DevOps Server connection settings are provided through the .NET configuration model
Tool calls use explicit per-request collection, project, and, where needed, repository parameters
Authentication is resolved through collection-specific PAT headers using the X-AzureDevOps-Pat-{CollectionName} pattern
The base organization URL is fixed at server startup and is not overridable per request

Included in This Release

.NET-based MCP runtime and tool registration for Azure DevOps Server scenarios
Reusable ASP.NET Core package for integrating the toolset into existing MCP servers
Work item read and write capabilities
Repository workflow support for branch and pull request creation
Work item linking between tracked work and repository artifacts