azure-cli-mcp-using-python

Created By
devanshjainmsa year ago
MCP server to access Azure using az commands.
Overview

what is azure-cli-mcp-using-python?

azure-cli-mcp-using-python is a project that provides a server to access Azure services using Azure CLI commands (az commands).

how to use azure-cli-mcp-using-python?

To use this project, set up the MCP server and execute Azure CLI commands through it to manage Azure resources.

key features of azure-cli-mcp-using-python?

  • Access Azure services using familiar az commands.
  • Simplified management of Azure resources.
  • Built with Python for easy customization and integration.

use cases of azure-cli-mcp-using-python?

  1. Managing Azure resources programmatically.
  2. Automating Azure deployments and configurations.
  3. Integrating Azure CLI commands into Python applications.

FAQ from azure-cli-mcp-using-python?

  • What is the purpose of this project?

The project allows users to interact with Azure services using Azure CLI commands through a Python-based server.

  • Is there any documentation available?

Yes, you can find the documentation on the project's GitHub page.

  • What programming language is used?

The project is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
devanshjainms
Star
0
Language
-
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago