Atlassian Cli MCP Server

Atlassian Cli MCP server exists for a simple reason — assistants are far more useful when they can act on Atlassian Cli directly instead of describing what you should do. A lightweight, native Go CLI for Atlassian Jira and Confluence.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Atlassian Cli is connected, these are the calls the assistant has available:

• jira_user — User authentication
• jira_issue — Get issue, subtasks
• jira_search — Search issues via JQL
• jira_create — Create issues
• jira_update — Update issues
• jira_delete — Delete issues
• jira_transition — Transition issues, get available transitions
• confluence_page — Get page content
• confluence_label — Label management
• confluence_restriction — Page restriction management
• Variable — Description
• JIRA_URL — Jira Cloud URL (e.g. https://your-domain.atlassian.net)

Configuration and credentials

You will need 8 environment variables: JIRA_URL, JIRA_EMAIL, JIRA_API_TOKEN, CONFLUENCE_URL, CONFLUENCE_EMAIL, CONFLUENCE_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_PERSONAL_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Atlassian Cli.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the atlassian cli mcp server does with a few real requests.

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Atlassian Cli's toolset — jira_user, jira_issue, jira_search and 11 more — is a fair guide to whether it matches your workflow. It is maintained by putcho01; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.