mcp server
Azure Boards MCP
Azure DevOps Boards work items over MCP (stdio). Requires Bun, org, project, and PAT.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Most recent push to the repository was 2026-06-25.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-06-25 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Aiqbee Brain
— last commit 2026-03-07, shares azure
AI knowledge graph for architecture, portfolio, and digital strategy management.
-
io.github.alexpota/cloudscope
— last commit 2026-08-04, shares azure
Azure + GCP cost management: spending, forecasts, anomalies, budgets, idle resources, and tags.
-
Cloudprice
— last commit 2026-08-02, shares azure
Compare on-demand compute + storage pricing across AWS, Azure, and GCP. Bulk workload compare.
-
nable
— last commit 2026-08-06, shares azure
Local-first FinOps copilot: ask AWS, Azure, GCP, Kubernetes and SaaS cost questions in your editor.
-
aden-hive-hive-browser-edge-cases
— last commit 2026-05-29, shares agent
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like L…
-
aden-hive-hive-hive-browser-automation
— last commit 2026-05-29, shares agent
Required before any browser_* tool call. Teaches the screenshot + browser_click_coordinate workflow that reaches shadow…
-
aden-hive-hive-hive-chart-creation-foundations
— last commit 2026-05-29, shares agent
Required reading whenever any chart_* tool is available. Teaches the one-tool embedding contract (call chart_render → l…
-
aden-hive-hive-hive-colony-progress-tracker
— last commit 2026-05-29, shares agent
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message inc…
-
aden-hive-hive-hive-context-preservation
— last commit 2026-05-29, shares agent
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
-
aden-hive-hive-hive-error-recovery
— last commit 2026-05-29, shares agent
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
These share tags the maintainers applied themselves, such as azure, agent. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: agent, azure, mcp.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab