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 that silently fail. a2atlassian fixes all of that:
Jira & Confluence for AI agents. Pre-configured connections, compact output.
Batch create-or-update with preserve-on-omit body semantics + per-page status + partial-failure shape
confluence_set_page_properties
Metadata-only write (page_width, emoji, labels) — physically cannot touch body or title
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
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 output — list_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
~35 (loaded on demand)
~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
Shipped: Jira full surface (v0.3.0) · Confluence core + markdown-to-storage with full CommonMark + GFM fidelity (v0.4.0, v0.5.2) · 1Password op:// token refs (v0.5.1) · metadata-only Confluence writes + preserve-on-omit body semantics (v0.5.2).
# Recommended
uv tool install a2atlassian
# Or with pip
pip install a2atlassian
# CLI
a2atlassian login -p myproject --url https://mysite.atlassian.net --email [email protected] --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 [email protected] "${CI_ATLASSIAN_TOKEN}"
Development
make bootstrap # Install deps + pnpm + git hooks
make check # Lint + test + coverage-diff + security (full gate)
make test # Tests with coverage
make lint # agent-harness + jscpd + actionlint (never modifies files)
make fix # Auto-fix + lint
make similar # Advisory: report similarly-named functions/classes
Linters: ruff + ty (via agent-harness), yamllint, jscpd (copy-paste
detection via pnpm), actionlint (GitHub Actions workflows). Pre-commit
hooks run agent-harness fix + lint on every commit. Install pnpm and
actionlint via brew install pnpm actionlint.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich A2atlassian?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt A2atlassian einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet A2atlassian?
A2atlassian läuft lokal über stdio.
Wann wurde A2atlassian zuletzt geprüft?
Zuletzt geprüft: 2026-11-09. Jira & Confluence for AI agents. Pre-configured connections, compact output.