Azure DevOps MCP is a dynamic MCP (Model Context Protocol) server that automatically switches the Azure DevOps authentication context based on the current working directory, enabling seamless access to multiple Azure DevOps organizations and projects from a single MCP server. It relies on per-repository local configuration files named .azure-devops.json, which specify organizationUrl, project, a PAT token, and tool settings (workItems, repositories, builds, pullRequests, pipelines) along with metadata. PAT tokens are stored locally per repository and are excluded fromGit. The server supports unlimited projects with isolated authentication, providing comprehensive Azure DevOps integration (work items, repositories, builds, pipelines, and more). Key capabilities include local configuration files, zero-configuration switching, dynamic environment/context detection, and robust error handling with graceful fallbacks to environment variables. Directory detection supports exact matches, nested directories, longest-match priority, parent-directory search, and a fallback to a default configuration. The MCP exposes commands for managing Azure DevOps operations (get-work-items, create-work-item, get-repositories, get-pull-requests, get-builds, trigger-pipeline, get-pipeline-status) and integrates with Claude Code for automatic context switching and secure contextual authentication. Security considerations cover HTTPS, per-request token handling, and avoidance of token caching.