v1.0.0 — Initial release

First tagged release of the Azure Files MCP connector — a read-only MCP server that gives
Claude access to one folder on an Azure Files share, enforcing each user's real NTFS
permissions rather than a blanket RBAC role.

What it does

• list_directory / read_file — read-only, nothing else. No write, delete, or rename
  tool exists anywhere in the codebase.
• Every file/folder access is checked against the calling user's actual NTFS permissions
  (including transitive AD group membership), evaluated in code against the real Windows
  security descriptor — not delegated to Azure RBAC, which has no per-user enforcement
  mechanism over REST.
• read_file returns readable text for plain text files, PDF, Word (.docx), and Excel
  (.xlsx) automatically. Legacy binary .doc/.xls and scanned/image-only PDFs aren't
  supported.
• Every call — granted, denied, or errored — is recorded in a structured audit log.

Setup

See SETUP.md for the full Entra ID / Azure Portal walkthrough, and
README.md for the architecture and design rationale. Reusable across clients
by changing configuration only (STORAGE_ACCOUNT_NAME, SHARE_NAME, ROOT_PATH, etc.) —
no code changes needed.

Requirements

• Target tenant's on-prem AD synced to Entra ID (Entra Connect / Cloud Sync) — NTFS
  enforcement depends on resolving on-premises AD SIDs.
• Single App Service instance only (the OAuth relay's in-flight sign-in state is in-process
  memory — see README.md's Architecture section before scaling out).

This release

azure-files-mcp-deploy.zip attached below is the deployable artifact — src/,
package.json, package-lock.json, and tsconfig.json only. Deploy it to a Linux App
Service (Node 20+) with SCM_DO_BUILD_DURING_DEPLOYMENT=true set; Azure's Oryx builder
compiles it fresh server-side. Full steps in SETUP.md Part 4.