How does authentication work?
The server leverages standard Azure authentication via the Azure CLI. Run `az login` before starting the server to provide credentials.
@danielealbano
Basic information
Category
Cloud & Infrastructure
Last updated
Transports
stdio
Author
danielealbano
Submitted by
Daniele Salvatore Albano
MCP server for the Azure DevOps Boards
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust. It enables AI assistants to manage work items, query boards, and run WIQL queries.
Install via Homebrew (macOS) or Scoop (Windows). Authenticate with az login. Configure your MCP client (e.g., Claude Desktop) to run the binary path. The server runs in stdio mode by default, or HTTP server mode with the --server flag and optional --port.
The server leverages standard Azure authentication via the Azure CLI. Run `az login` before starting the server to provide credentials.
Tools follow the naming convention `azdo_VERB_WHAT` (e.g., `azdo_create_work_item`, `azdo_list_teams`). The full list is documented in the README.
Yes, use the `--server` CLI flag. Optionally specify `--port` (default 3000). In HTTP mode, the server listens on all interfaces.
Pre-built binaries are available via Homebrew or Scoop. Building from source requires Rust. Azure CLI is required for authentication.
No. This project is not affiliated with, endorsed by, or sponsored by Microsoft. It uses standard Microsoft APIs.

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the
Model Context Protocol (MCP) server for Kubernetes and OpenShift

Build and run websites, APIs, automations, and admin tools from chat. Your agent creates the data, logic, pages, and scheduled jobs; Tessryx hosts them on your own domain. No code generated, nothing to deploy.
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
🧩 MCP Gateway - A lightweight gateway service that instantly transforms existing MCP Servers and APIs into MCP servers with zero code changes. Features Docker deployment and management UI, requiring no infrastructure modifications.
Comments