setup-atlassian-mcp

Configure Atlassian MCP integration with a personal API token.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/diegolirio/ai-showcase-skills --skill setup-atlassian-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-atlassian-mcp
Source: https://github.com/diegolirio/ai-showcase-skills/tree/main/skills/setup-atlassian-mcp
Command: npx skills add https://github.com/diegolirio/ai-showcase-skills --skill setup-atlassian-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the Atlassian MCP integration (Rovo) to securely authenticate with a Personal API Token using Basic auth, enabling seamless interaction with Jira and Confluence.

Core Features & Use Cases

  • Securely set up MCP endpoints and credentials for Jira/Confluence integration.
  • Supports global or local scope with flexible storage options for the credentials.
  • Merges or creates MCP configuration entries without overwriting existing servers, and validates JSON integrity.

Quick Start

Use this skill to configure MCP integration by following guided prompts to provide scope, storage mode, your Atlassian email, and API token.

Frequently Asked Questions about setup-atlassian-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Atlassian MCP integration with a personal API token?

To configure Atlassian MCP integration, you provide your Atlassian email and personal API token through guided prompts. The setup securely applies Basic authentication using base64 encoding to merge or create the atlassian-rovo-mcp entry in your .mcp.json file.

Can I store Jira MCP credentials in environment variables instead of the JSON config?

Yes, you can store Jira MCP credentials in environment variables. The setup supports flexible storage modes, allowing you to keep your Atlassian API token in environment variables or directly within the .mcp.json configuration file.

Does setting up the Atlassian Rovo MCP entry overwrite existing servers in .mcp.json?

No, setting up the Atlassian Rovo MCP entry does not overwrite existing servers. The process safely merges the new configuration into your .mcp.json file or creates the entry if it is missing, while validating JSON integrity.

What is the difference between global and local scope when configuring Confluence MCP?

Global and local scopes determine where the Confluence MCP configuration is applied. Global scope makes the integration available across your environment, while local scope restricts the configuration to a specific project or directory context.

Why do I need to base64 encode credentials for Atlassian MCP setup?

You need to base64 encode credentials for Atlassian MCP setup to implement secure Basic authentication. This encoding safely transforms your Atlassian email and API token into a format the Rovo MCP endpoint can validate.

Can I use this setup to configure MCP for both Jira and Confluence workflows?

Yes, you can use this setup to configure MCP for both Jira and Confluence workflows. It securely establishes the authentication needed to interact seamlessly with both Atlassian platforms through a single personal API token.