CosmosDBShell 1.0.213-preview

Azure Cosmos DB Shell

Lightweight CLI for Azure Cosmos DB.

Features

• Connect via Entra ID, connection string, or Azure CLI/Developer tools
• Navigate with ls and cd (Account → Databases → Containers → Items)
• Inspect the current location with pwd
• Create, query, delete: mkdb, mkcon, mkitem, query, rm
• Pipelines and scripting with variables, loops, functions
• MCP server for AI/tool integration

Quick Start

Requirements: .NET SDK 10.0+.

The .NET runtime alone is not enough for the commands below. dotnet run and dotnet tool install are SDK commands. To verify the SDK is installed, run dotnet --list-sdks.

dotnet run --project CosmosDBShell

Example session:

connect "AccountEndpoint=...;AccountKey=..."
ls                          # list databases
cd MyDatabase
ls                          # list containers
cd MyContainer
query "SELECT * FROM c"

Install from NuGet package artifacts

When consuming build artifacts (*.nupkg) from this repo, install as a .NET global tool.

dotnet tool install for these packages requires the .NET SDK 10.0+ because the tool packages target net10.0. Installing only the .NET runtime does not provide the dotnet tool command.

1. Download the base tool package (CosmosDBShell.<version>.nupkg) and the package for your runtime to the same local folder.
2. Install from that folder with --add-source using the base package ID CosmosDBShell.

Runtime-specific package files

• Linux x64: CosmosDBShell.linux-x64.<version>.nupkg
• Linux ARM64: CosmosDBShell.linux-arm64.<version>.nupkg
• macOS x64: CosmosDBShell.osx-x64.<version>.nupkg
• macOS ARM64: CosmosDBShell.osx-arm64.<version>.nupkg
• Windows x64: CosmosDBShell.win-x64.<version>.nupkg

Install command

After placing the base package and the matching runtime package in the same folder, install with the base package ID:

dotnet tool install --global CosmosDBShell --add-source /path/to/nupkgs --version <version>

Windows PowerShell example:

dotnet tool install --global CosmosDBShell --add-source C:\path\to\nupkgs --version <version>

Use, update, uninstall

Run the tool:

cosmosdbshell

Update:

dotnet tool update --global <package-id> --add-source /path/to/nupkgs --version <new-version>

Uninstall:

List the installed global tools first so you can identify the exact package ID:

dotnet tool list --global

Then uninstall the tool by its package ID:

dotnet tool uninstall --global CosmosDBShell

Documentation

• Connection - Authentication and connection options
• Commands - All shell commands
• Navigation - Navigation, pipes, CLI arguments
• Programming - Variables, control flow, functions
• MCP - Model Context Protocol integration

CI And Packaging

This repo currently uses one GitHub Actions workflow for validation and package artifacts:

• .github/workflows/validate-and-package.yml: runs validation on pull requests, and on branch pushes or manual runs it also builds installable RID-specific NuGet tool packages and uploads them as workflow artifacts

Local builds and GitHub Actions use the default NuGet sources (nuget.org). The Azure DevOps pipeline uses a restricted config at .pipelines/nuget.config that limits restores to the internal feed.

Packaging runs produce preview versions in the form 1.0.<run>-preview.<branch>, upload separate artifacts for each RID-specific package plus a pointer/base package artifact for the non-RID package ID, and the Azure pipeline publishes both the base package and the RID-specific packages to the internal feed.

Command-Line Arguments

Examples:

# Run a script and exit. Script arguments become $1, $2, ... inside the script.
cosmosdbshell -c "seed.csh mydb mycontainer" --connect "AccountEndpoint=...;AccountKey=..."

# Run a script from piped command text.
echo "seed.csh mydb mycontainer" | cosmosdbshell --connect "AccountEndpoint=...;AccountKey=..."

How to Contribute

This project welcomes contributions and suggestions. To contribute, see these documents:

• Code of Conduct
• Security
• Contributing

License

MIT