RyanCardin15 AzureDevOps MCP

WHAT IT CONNECTS

What RyanCardin15 AzureDevOps MCP gives an AI Agent

• List work items using WIQL queries
• Get work item details by ID
• Search for work items
• Get recently updated work items
• Get your assigned work items
• Create new work items
• Update existing work items
• Add comments to work items
• Update work item state
• Assign work items
• Create links between work items
• Bulk create/update work items
• Get team boards
• Get board columns
• Get board items
• Move cards on boards
• Get sprints
• Get the current sprint
• Get sprint work items
• Get sprint capacity
• Get team members
• List projects
• Get project details
• Create new projects
• Get areas
• Get iterations
• Create areas
• Create iterations
• Get process templates
• Get work item types
• Get work item type fields
• List repositories
• Get repository details
• Create repositories
• List branches
• Search code
• Browse repositories
• Get file content
• Get commit history
• List pull requests
• Create pull requests
• Get pull request details
• Get pull request comments
• Approve pull requests
• Merge pull requests
• Run automated tests
• Get test automation status
• Configure test agents
• Create test data generators
• Manage test environments
• Get test flakiness analysis
• Get test gap analysis
• Run test impact analysis
• Get test health dashboard
• Run test optimization
• Create exploratory sessions
• Record exploratory test results
• Convert findings to work items
• Get exploratory test statistics
• Run security scans
• Get security scan results
• Track security vulnerabilities
• Generate security compliance reports
• Integrate SARIF results
• Run compliance checks
• Get compliance status
• Create compliance reports
• Manage security policies
• Track security awareness
• Rotate secrets
• Audit secret usage
• Configure vault integration
• List artifact feeds
• Get package versions
• Publish packages
• Promote packages
• Delete package versions
• List container images
• Get container image tags
• Scan container images
• Manage container policies
• Manage universal packages
• Create package download reports
• Check package dependencies
• Get AI-powered code reviews
• Suggest code optimizations
• Identify code smells
• Get predictive bug analysis
• Get developer productivity metrics
• Get predictive effort estimations
• Get code quality trends
• Suggest work item refinements
• Suggest automation opportunities
• Create intelligent alerts
• Predict build failures
• Optimize test selection
• Node.js (v16 or later)
• TypeScript (v4 or later)
• An Azure DevOps account with a Personal Access Token (PAT) or appropriate on-premises credentials
• Clone the repository:
• Install dependencies:
• Configure environment variables (create a `.env` file or set them directly):
• Build the project:
• Start the server:
• Go to your Azure DevOps organization
• Click on your profile icon in the top right
• Select "Personal access tokens"
• Click "New Token"
• Give it a name and select the appropriate scopes:
• Work Items: Read & Write
• Code: Read & Write
• Project and Team: Read & Write
• Build: Read
• Release: Read
• Personal Access Token (PAT):
• Similar to cloud setup, but create the PAT in your on-premises instance
• Set `AZURE_DEVOPS_AUTH_TYPE=pat`
• NTLM Authentication:
• Use your Windows domain credentials
• Set `AZURE_DEVOPS_AUTH_TYPE=ntlm`
• Provide username, password, and domain
• Basic Authentication:
• Use your local credentials
• Set `AZURE_DEVOPS_AUTH_TYPE=basic`
• Provide username and password
• Simple setup with organization URL and PAT
• Default configuration expects format: `https://dev.azure.com/your-organization`
• Always uses PAT authentication
• Sample configuration files provided in `.env.cloud.example`
• Requires additional configuration for server URL, collection, and authentication
• URL format varies based on your server setup: `https://your-server/tfs`
• Requires specifying a collection name
• Supports multiple authentication methods (PAT, NTLM, Basic)
• May require API version specification for older server versions
• Sample configuration files provided in `.env.on-premises.example`
• `src/`
• `Interfaces/`: Type definitions for parameters and responses
• `Services/`: Service classes for interacting with Azure DevOps APIs
• `Tools/`: Tool implementations that expose functionality to clients
• `index.ts`: Main entry point that registers tools and starts the server
• `config.ts`: Configuration handling
• `WorkItemService`: Work item operations
• `BoardsSprintsService`: Boards and sprints operations
• `ProjectService`: Project management operations
• `GitService`: Git repository operations
• `TestingCapabilitiesService`: Testing capabilities operations
• `DevSecOpsService`: DevSecOps operations
• `ArtifactManagementService`: Artifact management operations
• `AIAssistedDevelopmentService`: AI-assisted development operations
• `WorkItemTools`: Tools for work item operations
• `BoardsSprintsTools`: Tools for boards and sprints operations
• `ProjectTools`: Tools for project management operations
• `GitTools`: Tools for Git operations
• `TestingCapabilitiesTools`: Tools for testing capabilities operations
• `DevSecOpsTools`: Tools for DevSecOps operations
• `ArtifactManagementTools`: Tools for artifact management operations
• `AIAssistedDevelopmentTools`: Tools for AI-assisted development operations
• Open the `src/index.ts` file
• Add new tool registrations following the pattern of existing tools
• Build and restart the server
• Ensure your Personal Access Token is valid and has the required permissions
• Check that the organization URL is correct
• Use `npm run build:ignore-errors` to bypass TypeScript errors
• Check for missing or incorrect type definitions
• Verify that the Azure DevOps project specified exists and is accessible
• Fork the repository
• Create a feature branch (`git checkout -b feature/amazing-feature`)
• Commit your changes (`git commit -m 'Add some amazing feature'`)
• Push to the branch (`git push origin feature/amazing-feature`)
• Open a Pull Request