azure-devops-attachment-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_DEVOPS_PAT | Yes | Personal Access Token. Sent only as a Basic auth header to AZURE_DEVOPS_URL; never logged. | |
| AZURE_DEVOPS_URL | Yes | Collection URL, e.g. https://tfs.company.local/tfs/DefaultCollection. Include the /tfs/<Collection> path used by your server. | |
| AZURE_DEVOPS_PROJECT | No | Default team project for the attachment endpoints. The work item's own project takes precedence when known. | |
| AZURE_DEVOPS_API_VERSION | No | REST api-version. 7.0 = Azure DevOps Server 2022, 6.0 = 2020, 5.0 = 2019. | 7.0 |
| AZURE_DEVOPS_DOWNLOAD_DIR | No | Directory where download_attachment saves files when no outputDir is given. | |
| AZURE_DEVOPS_ALLOW_INSECURE_TLS | No | Set to true to accept self-signed certificates. Insecure; prefer NODE_EXTRA_CA_CERTS=/path/to/ca.pem. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_attachmentsA | List the file attachments of an Azure DevOps work item: name, size, comment, created date, attachment id (GUID) and URL. |
| add_attachmentA | Upload a local file and attach it to a work item (adds an AttachedFile relation). Simple upload limit: 130 MB. Returns the attachment id and the work item's new revision. |
| delete_attachmentA | Remove an attachment from a work item by attachment id or by a file name that is unique on the work item. Only the link is removed; Azure DevOps has no API to delete the stored file. |
| download_attachmentA | Download a work item attachment to a local directory by attachment id or unique file name. Existing files are never overwritten (a " (n)" suffix is added). Returns the absolute path of the saved file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool performs a clearly distinct action on attachments: list, upload, delete, and download. There is no overlap in purpose, and the descriptions reinforce the boundaries.
All tool names follow a consistent verb_noun snake_case pattern: list_attachments, add_attachment, delete_attachment, download_attachment. The only minor variation is singular versus plural attachment, but it reads naturally and does not cause confusion.
Four tools is exactly the right scope for an attachment management server: list, add, delete, and download. There is no redundancy or unnecessary bloat.
The tool set covers the full actionable lifecycle for work item attachments: enumerate, add, remove the link, and retrieve the file. Update is not applicable since attachments are immutable, so there are no meaningful gaps.