Connect Azure Blob Storage to Claude Code

Let Claude upload, organize, and clean up blobs in Azure Blob Storage. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Azure Blob Storage to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Azure Blob Storage, you add a Azure Blob Storage MCP server: a small hosted service that exposes Azure Blob Storage's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Azure Blob Storage account. No API keys pasted into config files.

claude mcp add --transport http azure-blob-storage https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Azure Blob Storage once connected?

Full read-write Azure Blob Storage access lets Claude upload a blob to a specific container and prefix, copy or move blobs between locations, set blob metadata and access tiers, generate a SAS URL, and delete blobs once you approve. The container housekeeping that used to mean the portal or az CLI happens through the assistant.

Upload a blob to a specific container and prefix
Copy or move blobs between containers or prefixes
Set or update blob metadata and access tier for lifecycle and cost tracking
Generate a scoped SAS URL for a single blob after you approve it
Delete a blob or a scoped set of blobs once you confirm
List a prefix and propose a batched reorganization for review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Azure Blob Storage access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Azure Blob Storage API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Azure Blob Storage changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Azure Blob Storage connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Azure Blob Storage connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Azure Blob Storage account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Azure Blob Storage's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Azure Blob Storage?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Azure Blob Storage account it signs in with. Revoking access is one click in Azure Blob Storage.

More on the Azure Blob Storage connector

Azure Blob Storage connector for claude.ai Amazon S3 + Claude Code Egnyte + Claude Code Google Cloud Storage + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us