microsoft/mcp is a repository of Microsoft’s Model Context Protocol server implementations, which let AI applications connect to data sources and tools through a shared client-server interface. It supports Microsoft MCP server contributors and the catalogue entries are add-ons for working with these servers.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/microsoft/mcpnpx agentmods add skills/microsoft/mcp/add-azure-mcp-toolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/mcp/add-azure-mcp-tools)<a href="https://agentmods.dev/skills/microsoft/mcp/add-azure-mcp-tools"><img src="https://agentmods.dev/badge/skills/microsoft/mcp/add-azure-mcp-tools/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/microsoft/mcp/add-azure-mcp-tools"><img src="https://agentmods.dev/badge/skills/microsoft/mcp/add-azure-mcp-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.20629 |
| Opus 5.5 | $0.00024 | $0.08252 |
| Sonnet 5.5 | $0.00012 | $0.04126 |
| Haiku 4.5 | $0.00006 | $0.02063 |
Grade A, and why
add-azure-mcp-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 2,136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New Tool to Azure MCP
Purpose
Step-by-step workflow for adding a new command to any Azure MCP toolset. Each phase has an explicit gate — do not proceed until the gate passes.
Decision: New Toolset or Existing?
Before starting, determine:
- Adding to existing toolset? → Skip to Phase 1.
- Creating a new toolset? → Complete Phase 0 first.
⚠️ CRITICAL: Does your command interact with Azure resources?
| Azure Service Commands | Non-Azure Commands | |
|---|---|---|
| Examples | ACR Registry List, SQL Database List, Storage Account Get | CLI wrappers, Best Practices, Documentation tools |
| test-resources.bicep | ✅ Required | ❌ Skip |
| test-resources-post.ps1 | ✅ Required (even if basic) | ❌ Skip |
| RBAC role assignments | ✅ Required | ❌ Skip |
| Live tests | ✅ Required (recorded) | ❌ Skip |
| Unit tests | ✅ Required | ✅ Required |
Security Requirements
Terminology note: In this repo, tool refers to the MCP-exposed capability and command refers to the underlying C# command class implementation. Both terms appear in the codebase and docs.
All tool inputs are untrusted. These requirements apply at every phase and are not optional.
Input Validation
- Validate inputs against the specific naming rules of the Azure resource being targeted (length, allowed characters, casing). Do not apply a generic blocklist — Azure resource naming rules vary significantly by service.
- Example: Storage account names are 3–24 lowercase alphanumeric characters only.
- Example: Resource group names allow letters, digits, underscores, hyphens, and periods up to 90 characters.
- Reference: Azure naming rules and restrictions
- Use
ValidateOptionsfor semantic constraints beyond nullability (name length, format, mutual exclusivity, and allowed value sets). Only reject characters that are provably invalid for the specific resource type. This applies to both the new two-genericSubscriptionCommandpattern and the legacy one-generic pattern — see theValidateOptionsoverride guidance in Phase 1d. - Prefer SDK/runtime validators and deterministic checks first (
Length, explicit allowed-value sets, character/category checks).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago Changed · +2 lines 3e5114b43437
- 29d ago Changed · +22 lines 2fd976194a97
- 1mo ago Changed dc961426e7c4
- 1mo ago Changed · +2 lines f03abd9f2bf4
- 1mo ago Changed · +13 lines e1475615ad5b
- 1mo ago First seen · 2,097 lines · 59 tokens per session scan A ed0b004d6637
add-azure-mcp-tools is a skill published in the GitHub repository microsoft/mcp (3,800 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 20,629 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.