In today's world everything is automated. Everything is fast. Everything is AI-driven.
If you're not leveraging the power of AI, you'll soon fall behind.
In this short article, I'll show you how developers, managers, and product owners can save serious time when building and managing tickets, documentation, and planning.
So many times in my career, I've created detailed plans for clients - defining architecture, breaking down concepts, structuring execution. After everything gets approved, what happens next?
● We manually create tickets.
● We define scope again.
● We divide work into sprints.
● We repeat everything inside tools.
That part is time-consuming and boring.
But 2025 brings us tools that help us focus on solutions - not repetitive documentation.
Let’s set it up properly.
To connect Claude with Atlassian products like Jira and Confluence, we need to install the Atlassian MCP server.
Run:
1claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcpOr, if you already have a token:
1claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp --header "Authorization: Bearer YOUR_API_TOKEN_HERE"2. Click Create API token with scopes
3. Give it a meaningful name
4. Choose expiration (1-365 days)
6. Select scopes (define permissions)
7. Click Create
8. Copy and securely store the token - ⚠️ You cannot recover it later
We recommend saving it in a password manager.
Add Confluence and Jira API keys. When you create your API token for workflow automation, you should have something like this:
After generating your Atlassian API token, you need to store it securely as environment variables. The setup depends on your operating system.
1️⃣ Temporary (current terminal session only)
1export ATLASSIAN_API_TOKEN=your_token_here2export ATLASSIAN_EMAIL=your_email_hereThis will work until you close the terminal.
Permanent (recommended)
Add the variables to your shell profile file. If you use bash:
1nano ~/.bash_profileAdd:
1export ATLASSIAN_API_TOKEN=your_token_here2export ATLASSIAN_EMAIL=your_email_hereSave the file, then reload it:
1source ~/.bash_profile2️⃣ Option 2 - Permanent (Recommended)
1. Open Start
2. Search for Environment Variables
3. Click Edit the system environment variables
4. Click Environment Variables
5. Under User variables, click New
6. Add:
7. Repeat for:
8. Click OK and restart your terminal
Linux/macOS
1echo $ATLASSIAN_EMAILWindows PowerShell
1echo $env:ATLASSIAN_EMAILIf you see your value printed, you're ready.
Check installed MCP servers:
1claude mcp listYou should see the Atlassian MCP listed.
You should see something like this - and by "like" we mean you need one more step to actually authenticate with Atlassian products.
You have to see a similar message which only differs in the word Connected.
1. Open the Claude CLI
2. Navigate to /mcp
3. You will see all connected MCP servers
4. Select Atlassian
5. Authenticate
Then you should see the menu with all connected MCP servers. Select the desired MCP, such as Atlassian, and authenticate. Close and reopen Claude.
Next time you open /mcp, you'll see it fully connected and authenticated.
This is just one of the blogs in an incoming series which can help you automate your workflow and focus on problems and solutions instead of tools and usage of them and how creators imagine the feature should work. 🙂
Have a nice day and happy CODING/MANAGING!!!
