AWS Documentation MCP Server
MCP setupDevOps and cloud
FreeMCP setupDevOps and cloud
Start Microsoft's Azure MCP server via npx and let the agent work with Azure storage, Monitor logs and Cosmos DB using your az login.
npx workspacetemplates add azure-mcp --tool claude-codeWrites 1 file to your project root
{
"mcpServers": {
"azure": {
"command": "npx",
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
}
}npx workspacetemplates add azure-mcp --tool codexWrites 1 file to ~/.codex/
[mcp_servers.azure]
command = "npx"
args = ["-y","@azure/mcp@latest","server","start"]npx workspacetemplates add azure-mcp --tool cursorWrites 1 file to .cursor/
{
"mcpServers": {
"azure": {
"command": "npx",
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
}
}npx workspacetemplates add azure-mcp --tool gemini-cliWrites 1 file to .gemini/
{
"mcpServers": {
"azure": {
"command": "npx",
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
}
}npx workspacetemplates add azure-mcp --tool copilotWrites 1 file to .vscode/
{
"servers": {
"azure": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
}
}The Azure MCP server gives an agent tools for Azure Blob storage, Azure Monitor queries and metrics, and Cosmos DB NoSQL data. The old Azure/azure-mcp repository is archived; development moved to microsoft/mcp, which is where this setup comes from.
It authenticates with the Azure Identity SDK, so run az login first and the server acts as you. It has no documented read-only flag, so use an Azure role that only grants read access.
you › Query the app-prod Log Analytics workspace for errors in the last hour and group them by operation name.
agent › 214 errors: POST /checkout 131, GET /cart 58, POST /login 25. The checkout errors started at 14:12.MCP setupDevOps and cloud
FreeMCP setupDevOps and cloud
FreeMCP setupDevOps and cloud
FreeMCP setupDevOps and cloud
Free