Summary
Work-item bookkeeping, done from where the work happens.
Coverage runs the full width of the object: create, read, update, delete, link, search and batch. The batch pair is what makes it useful beyond one-offs — 200 items read or a mixed set of creates, updates and deletes in a single request, rather than a call per ticket.
What it is
A TypeScript MCP server for Azure DevOps Work Items, built on the Azure DevOps REST API.
What you get
- Work items created by type and title, with optional project, description, area path, iteration path, assignee and tags
- A work item read by ID with a chosen field list, or as a summary when the full record is more than you need
- Fields updated, with an optional comment recorded on the change
- Work items deleted to the recycle bin, or destroyed permanently when that is what you mean
- Batch reads of up to 200 work items, and batch updates that create, update or delete in a single request
- Search across title, description and ID with filters for project, type, state, assignee, tags, creation and update dates, ordering and a result cap up to 200
- Projects listed, and a single project's details fetched by ID or name
- Git commits linked to work items, parent links set, and attachments listed
Requirements
An Azure DevOps organisation and credentials for its REST API. The server detects a default project, so `projectName` is optional on most calls and only needed when you are working outside that default. Documentation is written in Traditional Chinese.