atlas-cli-tool 1.15.0

atlas-cli

A .NET CLI tool for interacting with Jira, Confluence, and Bitbucket Cloud.

Features

• Jira — work items (issues) and projects
• Confluence — spaces and pages
• Bitbucket — workspaces, repositories, and pipelines (status, steps, logs, run/stop)
• Auth — token-based authentication management with multi-account, scoped Bitbucket login, and per-repo access tokens
• Permissions — manage allowed Confluence spaces

Installation

dotnet tool install --global atlas-cli

Usage

# Authenticate
atlas-cli auth login

# Jira
atlas-cli jira workitem list
atlas-cli jira project list

# Confluence
atlas-cli confluence space list
atlas-cli confluence page list

# Bitbucket
atlas-cli bitbucket repo list      --workspace WS
atlas-cli bitbucket pipeline list  --workspace WS --repo REPO
atlas-cli bitbucket pipeline view  --workspace WS --repo REPO --id 42
atlas-cli bitbucket pipeline log   --workspace WS --repo REPO --id 42 --tail 200

# Output format
atlas-cli --format json jira workitem list

Bitbucket Authentication

Bitbucket Cloud rejects Atlassian API tokens that were not created with Bitbucket scopes. atlas-cli supports three independent ways to authenticate to Bitbucket — in increasing specificity:

1. Shared Atlassian credentials — works only if the API token used in auth login was created with Bitbucket scopes (read:repository:bitbucket, read:pipeline:bitbucket, etc.). No extra setup needed.
2. Account-level Bitbucket credentials — a separate Atlassian API token with Bitbucket scopes (Basic), or any Bitbucket access token (Bearer):

   atlas-cli auth bitbucket-login --mode basic  --email you@co.com --token <ATATT…> --workspace WS
   atlas-cli auth bitbucket-login --mode bearer --token <ATCTT…> --workspace WS
   atlas-cli auth bitbucket-set-workspace WS    # set or change the default workspace
   atlas-cli auth bitbucket-logout              # clear Bitbucket creds (Atlassian creds preserved)
   

3. Per-repo access tokens — for environments where IT restricts org/workspace tokens but you can mint repo-scoped ones (Bitbucket → Repository settings → Access tokens):

   atlas-cli auth bitbucket-add-repo-token    --workspace WS --repo REPO --token <ATCTT…>
   atlas-cli auth bitbucket-remove-repo-token --workspace WS --repo REPO
   atlas-cli auth bitbucket-list-tokens       # show all Bitbucket creds + per-repo tokens
   

When a per-repo token is registered for the workspace+repo of a request, it is preferred over the account-level Bitbucket credentials, which are in turn preferred over the shared Atlassian credentials. After setting a default workspace via bitbucket-set-workspace, the --workspace flag becomes optional on every bitbucket repo/bitbucket pipeline command.

MCP Server

atlas-cli includes a built-in Model Context Protocol server, allowing AI assistants (Claude Desktop, Cursor, etc.) to interact with Jira and Confluence directly.

# Start the MCP server over stdio
atlas-cli mcp

Claude Desktop Configuration

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "atlas-cli": {
      "command": "atlas-cli",
      "args": ["mcp"],
      "env": {
        "ATLAS_CLI_DOMAIN": "mycompany",
        "ATLAS_CLI_EMAIL": "user@example.com",
        "ATLAS_CLI_API_TOKEN": "<your-api-token>",
        "ATLAS_CLI_SKIP_ALLOWLIST": "true"
      }
    }
  }
}

Available MCP Tools

Jira:

Confluence:

Bitbucket:

Admin:

Environment Variables

Build

Requires .NET 10 SDK.

dotnet build
dotnet pack
dotnet tool install --global --add-source ./nupkg atlas-cli