A2atlassian
About
Give AI agents access to Jira and Confluence. Save credentials once, work from anywhere.
Details
- Author
- agentic-eng
- Downloads
- 296
- Categories
- Other, Project Management, Productivity
Jump to
- No Docker required – install with pip or uv tool
- Read‑only by default, write access opt‑in per connection
- Pre‑configured connections registered via --register
- Connection scoping with --scope limits agent visibility
- Compact TSV output saves 30‑60% tokens for list results
- Dynamic tool loading reduces context size (Claude Code)
- Error enrichment with field suggestions and auto‑fixed quirks
- Built‑in rate‑limiting retry with exponential backoff
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
A2atlassianCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install a2atlassian with pip install a2atlassian or uv tool install a2atlassian. Use it as an MCP server by running uvx --from a2atlassian a2atlassian-mcp with optional --register or --scope arguments, or as a CLI with commands like a2atlassian login. Configuration is managed via .mcp.json files and environment variable references.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"a2atlassian": {
"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>"
}
}
}
}
}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>"
}
}
}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 Docker — pip 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
> Scope today: full Jira surface (issues, comments, sprints, boards, worklogs, links, versions, fields, watchers, projects) and Confluence core (pages CRUD, search, metadata-only writes).
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
