atli - a CLI for Jira and Confluence, powered by mcp-atlassian
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-atlassian-cli","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# atli `atli` is a command-line interface for Jira, Confluence, and Bitbucket. It exposes every operation of [mcp-atlassian](https://pypi.org/project/mcp-atlassian/) as an ordinary shell command — no MCP client, server process, or daemon. Tools are discovered at startup from the mcp-atlassian server itself, so new tools appear automatically with pinned versions. The server comes from an install extra: `[atlassian]` (Jira + Confluence) or `[bitbucket]` ([mcp-atlassian-with-bitbucket](https://github.com/jellythomas/mcp-atlassian-with-bitbucket) — Jira, Confluence, **and** Bitbucket). ``` atli tools # list what your credentials unlock atli jira get-issue --issue-key PROJ-1 # markdown, verbatim from the tool atli confluence search --query "deploy" atli bitbucket list-repositories # with the [bitbucket] extra atli --profile work jira search --jql "assignee = currentUser()" ``` ## Install Jira + Confluence (upstream mcp-atlassian): ```console $ pipx install "mcp-atlassian-cli[atlassian]" ``` Bitbucket support (via the fork — Jira, Confluence, **and** Bitbucket): ```console $ pipx install "mcp-atlassian-cli[bitbucket]" ``` A bare `pipx install mcp-atlassian-cli` (no extra) installs the CLI without a server: the first tool command fails with a message naming both extras. The two providers are mutually exclusive — both ship the same `mcp_atlassian` package, so installing one over the other or uninstalling either corrupts the shared files (pip only refuses when both extras are requested in a single install). To switch providers, start fresh: `pipx uninstall mcp-atlassian-cli && pipx install "mcp-atlassian-cli[bitbucket]"`. With plain `pip` (no pipx venv to recreate), uninstall the provider and fastmcp distributions before switching — pip skips file writes while a package reads as installed, and it cannot undo two other overlaps: the providers share `mcp_atlassian`, and `fastmcp>=3` (upstream's pin) is a meta-package whose `fastmc…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.