azure-devops-work-items-mcp
An MCP server for Azure DevOps work items: get, list/filter, create, and
update. Filtering supports state, work item type, assignee, and area path
directly, plus an open-ended custom_filter parameter that accepts a raw
WIQL WHERE-clause fragment for anything else (sprint, priority, tags, date
ranges, OR-logic).
No organization, project, or credentials are built in — everything is supplied via environment variables at runtime.
Configuration
Three environment variables are required:
| Variable | Description |
|---|---|
AZURE_DEVOPS_ORG |
Your Azure DevOps organization name (the part after dev.azure.com/ in your URL) |
AZURE_DEVOPS_PROJECT |
The project name within that organization |
AZURE_DEVOPS_PAT |
A Personal Access Token with Work Items: Read & Write scope, created at https://dev.azure.com/<your-org>/_usersSettings/tokens |
Usage with Claude Desktop (or any MCP client using uvx)
Add this to your MCP client's config (for Claude Desktop:
claude_desktop_config.json):
{
"mcpServers": {
"azure-devops": {
"command": "uvx",
"args": ["azure-devops-work-items-mcp"],
"env": {
"AZURE_DEVOPS_ORG": "your-org-name",
"AZURE_DEVOPS_PROJECT": "your-project-name",
"AZURE_DEVOPS_PAT": "your-personal-access-token"
}
}
}
}
Use the full absolute path to uvx (find it with which uvx on
macOS/Linux or where.exe uvx on Windows) if your client can't find it on
PATH — this is a known issue with some desktop apps not inheriting a full
shell PATH.
To pin to a specific version instead of always pulling the latest:
"args": ["azure-devops-work-items-mcp==1.0.0"].
Tools
ado_get_work_item(work_item_id)ado_list_work_items(state?, work_item_type?, assigned_to?, area_path?, custom_filter?, top?)ado_create_work_item(work_item_type, title, description?, assigned_to?, area_path?, iteration_path?, tags?)ado_update_work_item(work_item_id, title?, state?, description?, assigned_to?, area_path?, iteration_path?, tags?)
License
MIT
Metadata
Release files for azure-devops-work-items-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| azure_devops_work_items_mcp-1.0.1.tar.gz | 5.9 kB | Without provenance | Details for azure_devops_work_items_mcp-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| azure_devops_work_items_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for azure_devops_work_items_mcp-1.0.1-py3-none-any.whl |
Total release size: 13.8 kB
Release files / azure_devops_work_items_mcp-1.0.1.tar.gz
| Download URL | azure_devops_work_items_mcp-1.0.1.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e1ac99408afe51c9d6a4a78b4c584185564601bac507c20801c049452c6e924
|
|
BLAKE2b-256 checksum How to use checksums |
95564866fa25e81479b8664fad11c61fe1465e685354453c30ffcd12b7c48e64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / azure_devops_work_items_mcp-1.0.1-py3-none-any.whl
| Download URL | azure_devops_work_items_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81f8523e8cf3b839c08c08bfca9c7d6fa3f983fd90476aefaebfbbee0b27137c
|
|
BLAKE2b-256 checksum How to use checksums |
0900d336e0ba1fe410b4c409671f6eb70f5007683e8dcde65062001e41b1de89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for azure-devops-work-items-mcp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.