Azure MCP server

This Azure MCP Server enables interaction with Azure cloud services (Blob Storage, Cosmos DB, and App Configuration) through the Model Context Protocol framework. It allows Claude to directly perform Azure operations with proper authentication and logging.

Installation

Quick Installation via Smithery

The simplest way to install is using Smithery:

npx -y @smithery/cli install @mashriram/azure_mcp_server --client claude

Manual Installation

Follow these steps for manual installation:

1. Clone the repository to your local machine

2. Set up Azure credentials using one of these methods:

   • Set environment variables:
     • AZURE_STORAGE_ACCOUNT_URL - Your Azure Storage account URL
     • AZURE_COSMOSDB_ENDPOINT - Your Cosmos DB endpoint URL
     • AZURE_COSMOSDB_KEY - Your Cosmos DB access key
     • AZURE_APP_CONFIGURATION_ENDPOINT - Your App Configuration URL
   • Authenticate via Azure CLI by running az login

3. Configure Claude Desktop:

   • Find your configuration file:
     • macOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
     • Windows: %APPDATA%/Claude/claude_desktop_config.json
   • Add this configuration:

"mcpServers": {
  "mcp-server-azure": {
    "command": "uv",
    "args": [
      "--directory",
      "/path/to/repo/azure-mcp-server",
      "run",
      "azure-mcp-server"
    ]
  }
}

4. Install and launch the Claude desktop app

5. Test your setup by asking Claude to perform an Azure operation

Available Tools

Azure Blob Storage Operations

Container Management

• blob_container_create - Creates a container
  • Required: container_name
• blob_container_list - Lists all containers
• blob_container_delete - Deletes a container
  • Required: container_name

Blob Management

• blob_upload - Uploads a file to a container
  • Required: container_name, blob_name, file_content (Base64 encoded)
• blob_delete - Deletes a blob
  • Required: container_name, blob_name
• blob_list - Lists blobs in a container
  • Required: container_name
• blob_read - Reads blob content
  • Required: container_name, blob_name

Azure Cosmos DB Operations

Container Operations

• cosmosdb_container_create - Creates a container
  • Required: container_name, partition_key
  • Optional: database_name (defaults to "defaultdb")
• cosmosdb_container_describe - Gets container details
  • Required: container_name
  • Optional: database_name
• cosmosdb_container_list - Lists all containers
  • Optional: database_name
• cosmosdb_container_delete - Deletes a container
  • Required: container_name
  • Optional: database_name

Item Operations

• cosmosdb_item_create - Creates a new item
  • Required: container_name, item (JSON object)
  • Optional: database_name
• cosmosdb_item_read - Reads an item
  • Required: container_name, item_id, partition_key
  • Optional: database_name
• cosmosdb_item_replace - Updates an existing item
  • Required: container_name, item_id, partition_key, item (JSON object)
  • Optional: database_name
• cosmosdb_item_delete - Deletes an item
  • Required: container_name, item_id, partition_key
  • Optional: database_name
• cosmosdb_item_query - Queries items using SQL
  • Required: container_name, query
  • Optional: database_name, parameters

Azure App Configuration Operations

• app_configuration_kv_read - Reads key-values
  • Optional: key (supports wildcards), label
• app_configuration_kv_write - Creates/updates a key-value
  • Required: key, value
  • Optional: label, content_type
• app_configuration_kv_delete - Deletes a key-value
  • Required: key
  • Optional: label

Important Notes

• Cosmos DB partition keys are required and must match the item being accessed
• All operations are case-sensitive when referencing Azure resources
• If not specified, the default database name is "SampleDB"
• All operations performed through this server are automatically logged and accessible via the audit://azure-operations resource endpoint

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.