Azure MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_COSMOSDB_KEY | Yes | The primary or secondary key for your Azure Cosmos DB account. Important: Treat this key like a password and keep it secure. | |
| AZURE_COSMOSDB_ENDPOINT | Yes | The endpoint URL for your Azure Cosmos DB account. | |
| AZURE_STORAGE_ACCOUNT_URL | Yes | The URL of your Azure Storage account (e.g., 'https://<your_account_name>.blob.core.windows.net'). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blob_container_createC | Create a new Blob Storage container |
| blob_container_listB | List all Blob Storage containers |
| blob_container_deleteC | Delete a Blob Storage container |
| blob_uploadC | Upload a blob to Blob Storage |
| blob_deleteC | Delete a blob from Blob Storage |
| blob_listC | List blobs in a Blob Storage container |
| blob_readC | Read a blob's content from Blob Storage |
| cosmosdb_container_createC | Create a new Cosmos DB container |
| cosmosdb_container_describeB | Get details about a Cosmos DB container |
| cosmosdb_container_listC | List all Cosmos DB containers in a database |
| cosmosdb_container_deleteC | Delete a Cosmos DB container |
| cosmosdb_item_createC | Create a new item in a Cosmos DB container |
| cosmosdb_item_readC | Read an item from a Cosmos DB container |
| cosmosdb_item_replaceC | Replace an item in a Cosmos DB container |
| cosmosdb_item_deleteC | Delete an item from a Cosmos DB container |
| cosmosdb_item_queryC | Query items in a Cosmos DB container using SQL |
| app_configuration_kv_readC | Read key-values from Azure App Configuration |
| app_configuration_kv_writeB | Write or update a key-value in Azure App Configuration |
| app_configuration_kv_deleteC | Delete a key-value from Azure App Configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Azure Operations Audit Log | A log of all Azure operations performed through this server |
TDQS
Scored across 19 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by Azure service (App Configuration, Blob Storage, Cosmos DB) and specific resource/action pairs, making it easy for an agent to select the correct tool without confusion. For example, blob_read and blob_upload target different operations on the same resource, but their names clearly differentiate them.
All tool names follow a consistent verb_noun pattern with underscores, such as 'app_configuration_kv_delete' and 'cosmosdb_item_query'. The naming is highly predictable across all 19 tools, using a service_resource_action structure that enhances readability and agent usability. There are no deviations in style or convention.
With 19 tools, the count is slightly high but reasonable for covering multiple Azure services (App Configuration, Blob Storage, Cosmos DB). Each tool earns its place by providing specific CRUD operations, though it might feel a bit heavy compared to more focused servers. The scope is well-defined, avoiding extreme bloat.
The tool set offers complete CRUD/lifecycle coverage for each Azure service domain. For Blob Storage and Cosmos DB, it includes create, read, update (via replace or write), delete, and list operations, with no obvious gaps. App Configuration has read, write, and delete, covering its key-value management needs effectively.