setup

A setup guide for connecting an Azure MCP server to Microsoft Azure using Azure CLI authentication. Azure is Microsoft's cloud platform, and Azure CLI is its command-line tool.

In plain words
What is it for?
Use it to check Azure CLI and Node.js, authenticate with Azure, and prepare the Azure MCP connection.
Why use it?
It checks the required software and login state, then explains what to install or run when something is missing.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/fcakyon/claude-codex-settings/setup
Clone the repo
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 461 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00461
Opus 5 $0.00004 $0.00230
Sonnet 5 $0.00002 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured yesterday against content hash 7f44e6fc1454, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

setup scanned grade D with 3 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 yesterday.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Linux: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- Linux: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Linux: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
plugins/azure-tools/commands/setup.md · 93 lines

What it actually says

Azure Tools Setup

Configure the Azure MCP server with Azure CLI authentication.

Step 1: Check Prerequisites

Check if Azure CLI is installed:

az --version

Check if Node.js is installed:

node --version

Report status based on results.

Step 2: Show Installation Guide

If Azure CLI is missing, tell the user:

Azure CLI is required for Azure MCP authentication.

Install Azure CLI:
- macOS: brew install azure-cli
- Linux: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
- Windows: winget install Microsoft.AzureCLI

After installing, restart your terminal and run this setup again.

If Node.js is missing, tell the user:

Node.js 20 LTS or later is required for Azure MCP.

Install Node.js:
- macOS: brew install node@20
- Linux: curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash - && sudo apt-get install -y nodejs
- Windows: winget install OpenJS.NodeJS.LTS

After installing, restart your terminal and run this setup again.

Step 3: Check Authentication

If prerequisites are installed, check Azure login status:

az account show

If not logged in, tell the user:

You need to authenticate to Azure.

Run: az login

This opens a browser for authentication. After signing in, you can close the browser.

Step 4: Verify Configuration

After authentication, verify:

  1. Read ${CLAUDE_PLUGIN_ROOT}/.mcp.json to confirm Azure MCP is configured
  2. Tell the user the current configuration

Step 5: Confirm Success

Tell the user:

Azure MCP is configured!

IMPORTANT: Restart Claude Code for changes to take effect.
- Exit Claude Code
- Run `claude` again

To verify after restart, run /mcp and check that 'azure' server is connected.

Reference: https://github.com/microsoft/mcp/tree/main/servers/Azure.Mcp.Server
Changes

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.

  1. yesterday First seen · 93 lines · 8 tokens per session scan D 7f44e6fc1454

Subscribe to this mod's changes

setup is a command published in the GitHub repository fcakyon/claude-codex-settings (1,114 stars, last pushed 2d ago), licensed Apache-2.0. It adds 8 tokens to every session and 461 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.