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
基本情報
MCP server for the Azure DevOps Boards
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
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.
Development environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack.
Deploy and manage SnapDeploy apps (Docker containers on AWS) from Claude Code, Cursor, Codex or Gemini CLI: builds, logs, env vars, add-ons, domains.
🧩 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.

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
Official OutageDeck MCP server for vendor-published cloud and SaaS status, incident timelines, and observed uptime history.
コメント