atlas-cli-tool 1.17.0

atlas-cli

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

Features

• Jira — work items (issues), projects, and runtime discovery of system and custom fields
• 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
atlas-cli jira field list --query customer

# 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

Configuration

Permission checks for Jira projects and Confluence spaces are enabled by default. They can be disabled globally so atlas-cli bypasses per-project and per-space approval entirely:

atlas-cli config set permission-checks disabled
atlas-cli config get

# Turn the checks back on
atlas-cli config set permission-checks enabled

The setting is stored at the top level of ~/.atlas-cli/config.json and applies to every account. The ATLAS_CLI_SKIP_ALLOWLIST environment variable remains available and, when set to true or false, overrides the persisted setting.

Permission checks are always non-interactive. When checks are enabled and a command targets a project or space that is not allowed, atlas-cli exits immediately with a nonzero status and prints the exact command needed to grant access. For example:

Access denied by atlas-cli: Jira project 'PROJ' is not allowed for action 'read'.
Grant access, then retry: atlas-cli permissions allow PROJ --type jira --actions read

Run the suggested command, then retry the original command. This behavior prevents scripts, MCP clients, and other AI tools from blocking while waiting for terminal input.

Dynamic Jira Fields

atlas-cli discovers Jira fields from the active site's metadata instead of relying on a fixed field list. You can inspect the global field catalog, the fields available while creating a particular issue type, or the fields editable on an existing issue:

atlas-cli jira field list --query customer
atlas-cli jira field create-meta --project PROJ --issue-type Story
atlas-cli jira field edit-meta PROJ-123

Create and edit commands accept additional fields as JSON. Field IDs are the safest identifiers; a unique field name is also accepted and resolved against the relevant create/edit metadata. Values are normalized using Jira's schema and allowed values where possible.

atlas-cli jira workitem create \
  --project PROJ \
  --type Story \
  --summary "Provision customer" \
  --fields-json '{"customfield_10123":{"id":"10001"},"Customer tier":"Gold"}'

atlas-cli jira workitem edit PROJ-123 \
  --fields-json '{"customfield_10456":"2026-10-15"}'

Create commands validate context-specific required fields before submitting the issue. Issue view and search output also includes nonstandard values under AdditionalFields, along with Jira's field name and schema when available.

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