Skip to main content
net10.0net8.0

Azure Blob Storage provider for GroupDocs MCP Framework. Supports SAS download URLs for output files.

Published
Sep 2, 2026
1mo ago
Total Downloads
339
339

Install

dotnet add package GroupDocs.Mcp.AzureBlob.Storage --version 26.9.0
ProductVersions
.NET
net10.0net8.0

README

GroupDocs.Mcp.AzureBlob.Storage

Azure Blob Storage IFileStorage implementation for the GroupDocs MCP Core framework.

Output files are exposed as time-limited SAS download URLs so MCP clients can fetch results directly from the blob container without streaming through the server.

Installation

dotnet add package GroupDocs.Mcp.Core
dotnet add package GroupDocs.Mcp.AzureBlob.Storage

Usage

Connection string

builder.Services
    .AddGroupDocsMcp()
    .AddAzureBlobStorage(options =>
    {
        options.ConnectionString = "DefaultEndpointsProtocol=https;AccountName=...;AccountKey=...";
        options.ContainerName    = "documents";
    });

Account name + key

options.AccountName   = "mystorage";
options.AccountKey    = "...";
options.ContainerName = "documents";

Managed identity / TokenCredential

options.AccountName     = "mystorage";
options.TokenCredential = new DefaultAzureCredential();
options.ContainerName   = "documents";

SAS URL generation requires the client to be able to sign — connection string / account key work out of the box; user-delegation SAS over TokenCredential requires the managed identity to hold the appropriate RBAC role.

Behaviour

  • Container is created on first use if missing (CreateIfNotExists).
  • Writes honor a rewrite flag; when false, colliding blob names get a (1), (2)… suffix.
  • GetDownloadUrlAsync returns a SAS URL (read-only) whose expiry is controlled by McpConfig.DownloadUrlExpiry (default: 1h). Returns null if the client cannot generate SAS.

Source: https://github.com/groupdocs/GroupDocs.Mcp.Core License: MIT

Changes from Previous Version

No structural changes between v26.4.1 and v26.9.0.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.