Skip to main content

Agent-to-Atlassian — CLI and MCP server for AI agents to work with Jira & Confluence.

Project description

🏢 a2atlassian

Agent-to-Atlassian

Give AI agents access to Jira and Confluence. Save credentials once, work from anywhere.

Jira + Confluence · read-only by default · pre-configured connections · compact TSV output

PyPI Python License CI MCP Registry

Quick Start · MCP Tools · Security · Comparison · Setup


Agent: "What's the status of PROJ-42? Add a comment with the progress update."
  ↓
a2atlassian → get issue, add comment, transition to In Progress
  ↓
Agent: "Done — PROJ-42 updated and moved to In Progress."

Why a2atlassian?

Existing Atlassian MCP servers (Rovo, sooperset) require Docker, .env files, and mcp-remote bridges. They dump 72 tools into agent context and have known quirks that silently fail. a2atlassian fixes all of that:

  • No Dockerpip install a2atlassian and you're done
  • Pre-configured connections — define projects in .mcp.json with --register, agent works immediately
  • Read-only by default — write access is opt-in per connection
  • Connection scoping--scope limits which projects an agent can see
  • Compact output — TSV for lists (30-60% fewer tokens), JSON for single entities
  • Dynamic tool loading — MCP clients that support deferred tools (e.g., Claude Code) load tools on demand, keeping context lean
  • Error enrichment — bad field names get suggestions, JQL typos get corrections, quirks get auto-fixed
  • Secrets stay in env${ATLASSIAN_TOKEN} in configs, expanded only at runtime

Quick Start

# Recommended — installs globally as a CLI tool
uv tool install a2atlassian

# Or with pip
pip install a2atlassian

As an MCP Server (recommended)

Claude Code (with pre-configured connection):

claude mcp add -s user a2atlassian -- uvx --from a2atlassian a2atlassian-mcp \
  --register myproject https://mysite.atlassian.net user@company.com '${ATLASSIAN_TOKEN}'

Claude Code (minimal — agent calls login on demand):

claude mcp add -s user a2atlassian -- uvx --from a2atlassian a2atlassian-mcp

Claude Desktop / Cursor / any MCP client (.mcp.json):

{
  "mcpServers": {
    "a2atlassian": {
      "command": "uvx",
      "args": [
        "--from", "a2atlassian", "a2atlassian-mcp",
        "--register", "myproject", "https://mysite.atlassian.net",
        "user@company.com", "${ATLASSIAN_TOKEN}"
      ],
      "env": {
        "ATLASSIAN_TOKEN": "your-api-token-here"
      }
    }
  }
}

Multiple projects:

{
  "args": [
    "--from", "a2atlassian", "a2atlassian-mcp",
    "--register", "myproject", "https://mysite.atlassian.net", "user@a.com", "${TOKEN_A}",
    "--register", "personal", "https://personal.atlassian.net", "user@b.com", "${TOKEN_B}"
  ]
}

Scoped connections (limit agent to specific saved projects):

{
  "args": ["--from", "a2atlassian", "a2atlassian-mcp", "--scope", "myproject"]
}

--register creates ephemeral in-memory connections (process lifetime, no files written). --scope filters which saved connections are visible. Both limit blast radius.

As a CLI

# Save a connection (validates by calling /myself)
a2atlassian login -p myproject \
  --url https://mysite.atlassian.net \
  --email user@company.com \
  --token "$ATLASSIAN_TOKEN"

# Enable writes
a2atlassian login -p myproject \
  --url https://mysite.atlassian.net \
  --email user@company.com \
  --token "$ATLASSIAN_TOKEN" \
  --no-read-only

# List / remove connections
a2atlassian connections
a2atlassian logout -p myproject

MCP Tools

Connection Management

Tool Description
login Save a connection — validates by calling /myself first
logout Remove a saved connection
list_connections List connections (no secrets exposed)

Jira — Read

Tool Description
jira_get_issue Get issue by key — full fields, status, assignee
jira_search Search by JQL with pagination — compact TSV output by default
jira_get_comments Get all comments for an issue
jira_get_transitions Discover available status transitions

Jira — Write (requires read-write connection)

Tool Description
jira_add_comment Add comment (wiki markup, API v2)
jira_edit_comment Update existing comment
jira_transition_issue Move issue to new status

Output Formats

All tools accept a format parameter:

Format Default for Description
toon Lists (search, comments) TSV with header — shape once, data many. 30-60% fewer tokens than JSON
json Single entities (get_issue) Standard JSON with metadata envelope

List responses use a compact TSV-style format (header row + tab-separated values) inspired by TOON. This is the same approach a2db uses — column names appear once, then just values. For a 50-issue search result, this typically saves 40-60% of tokens compared to JSON.

TSV example (search results):

# search (23 results, 50ms, truncated: False)
key	summary	assignee	status
PROJ-142	Fix auth timeout	Alice Smith	In Progress
PROJ-141	Add search filters	Bob Jones	To Do

JSON example (single issue):

{
  "data": {"key": "PROJ-142", "fields": {"summary": "Fix auth timeout", ...}},
  "count": 1,
  "truncated": false,
  "time_ms": 85
}

Error Enrichment

When something fails, a2atlassian tells the agent what to do:

Field 'asignee' does not exist
Did you mean: assignee?
Connection 'myproject' is read-only.
Run: a2atlassian login -p myproject --read-only false

Quirks handled automatically:

  • Assignee requires display name (not 712020: account IDs) — auto-detected with hint
  • Parent field must be plain string — {"key": "PROJ-14"} normalized to "PROJ-14" silently
  • Issue type conversion not supported via API — clear Jira UI instructions provided

Security

Read-Only by Default

Every connection starts read-only. Write tools check the connection flag before executing:

Connection 'myproject' is read-only.
Re-run 'a2atlassian login -p myproject --read-only false' to enable writes.

The human operator controls write access — not the agent.

Credential Storage

Connections saved via login go to ~/.config/a2atlassian/connections/ as TOML files:

  • File permissions: 0600 (owner read/write only)
  • ${ATLASSIAN_TOKEN} syntax — env var references stored literally, expanded at runtime
  • No secrets in outputlist_connections shows project name, URL, and mode — never tokens
  • Ephemeral mode--register keeps credentials in memory only, never written to disk

Connection Scoping

Use --scope to limit which saved connections a specific MCP instance can access:

# Project config — only myproject visible, even if other connections are saved
uvx --from a2atlassian a2atlassian-mcp --scope myproject

Project-level MCP configs (.claude/mcp.json) override global configs — each repo sees only its own connections.

Rate Limiting

Built-in retry with exponential backoff for Atlassian's rate limits (429) and transient server errors (500). Two retries at 1s and 3s intervals before surfacing the error.

Comparison

Feature a2atlassian Rovo (official) sooperset/mcp-atlassian
Setup pip install OAuth + Docker Docker + .env + mcp-remote
Tools in context 10 (Phase 1) ~72 ~72
Connection management TOML + --register + --scope Per-session OAuth .env file
Multi-project Yes (scoped) No One .env per setup
Read-only default Yes (per-connection) No No
Output format TSV + JSON JSON JSON
Error enrichment Field suggestions, quirk fixes Generic errors Generic errors
Quirk handling Auto-fix (assignee, parent) Documented workarounds Documented workarounds
Rate limiting Built-in retry No No
CLI Yes No No
License Apache 2.0 Proprietary MIT

Roadmap

Phase 1 (current): Jira core — get/search issues, comments (CRUD), transitions. The secondary critical path.

Phase 2: Full Jira surface — sprints, boards, links, projects, fields, worklogs, attachments, watchers.

Phase 3: Confluence — pages, comments, attachments, labels, search.

Setup by Environment

Local (macOS / Linux)

# Recommended
uv tool install a2atlassian

# Or with pip
pip install a2atlassian

# CLI
a2atlassian login -p myproject --url https://mysite.atlassian.net --email me@co.com --token "$TOKEN"

# Or add as MCP server (see Quick Start)

CI / Automation

uv tool install a2atlassian

# Pre-configured — no login needed
uvx --from a2atlassian a2atlassian-mcp --register ci https://mysite.atlassian.net ci-user@co.com "${CI_ATLASSIAN_TOKEN}"

Development

make bootstrap   # Install deps + hooks
make check       # Lint + test + security (full gate)
make test        # Tests with coverage
make lint        # Lint only (never modifies files)
make fix         # Auto-fix + lint

License

Apache 2.0


🏢 Agent-first Atlassian access since 2025.

Built by Denis Tomilin

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

a2atlassian-0.1.0.tar.gz (91.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

a2atlassian-0.1.0-py3-none-any.whl (18.8 kB view details)

Uploaded Python 3

File details

Details for the file a2atlassian-0.1.0.tar.gz.

File metadata

  • Download URL: a2atlassian-0.1.0.tar.gz
  • Upload date:
  • Size: 91.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for a2atlassian-0.1.0.tar.gz
Algorithm Hash digest
SHA256 f843ac00e7face094abc7969530c5fb36283a23ce8e89cdef26c25c6fc3a1e9c
MD5 62965e7f157acae3dd111253ac3a29d8
BLAKE2b-256 095e4b1ecd8cf33256c7b3a2623eabde49d9f67779919c2abb46493377f9bfdf

See more details on using hashes here.

Provenance

The following attestation bundles were made for a2atlassian-0.1.0.tar.gz:

Publisher: publish.yml on agentic-eng/a2atlassian

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file a2atlassian-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: a2atlassian-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 18.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for a2atlassian-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 53fb38821e2a127a779abc9f2474c91746fea2c0c12848863c766e6f312ffddf
MD5 00d52ceb7bceea3097d79e01b972553c
BLAKE2b-256 f275beebc1a5bd2626bc4f7bef1105c9f05611ad55be5a2bdbe675f796727519

See more details on using hashes here.

Provenance

The following attestation bundles were made for a2atlassian-0.1.0-py3-none-any.whl:

Publisher: publish.yml on agentic-eng/a2atlassian

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page