setup-atlassian-mcp-local-env

Configure Atlassian MCP locally using environment-stored credentials in .mcp.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures the Atlassian MCP integration (Rovo) for the local project using credentials stored in environment variables. The skill ensures a project-scoped MCP setup without prompts, defaulting to local scope and envvar storage.

Core Features & Use Cases

  • Local MCP configuration: Sets up the integration to talk to the MCP server using a local .mcp.json file.
  • Secret handling: Uses environment variables ATLASSIAN_MCP_CREDENTIALS to store Authorization tokens without prompting.
  • Guided bootstrap: Merges credentials into .mcp.json non-destructively when the file exists.

Quick Start

Create or update the local MCP configuration by providing Atlassian credentials in the environment and running the setup flow.

Frequently Asked Questions about setup-atlassian-mcp-local-env

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

FAQPage Schema
How do I configure Atlassian MCP integration locally using environment variables?

Configure Atlassian MCP integration locally by storing credentials in the ATLASSIAN_MCP_CREDENTIALS environment variable and running the setup flow to generate a local .mcp.json file. The skill reads the Authorization token directly from your shell environment without prompting for input.

What is the local .mcp.json file used for in single-repo Atlassian MCP setup?

The local .mcp.json file configures project-scoped Atlassian MCP integration for single-repo projects. It enforces a fixed local scope and merges environment-stored credentials non-destructively when the file already exists, ensuring your MCP setup remains isolated to the current project.

Can I set up Atlassian MCP credentials without being prompted for tokens?

Yes, you can set up Atlassian MCP credentials without prompts by defining ATLASSIAN_MCP_CREDENTIALS in your shell initialization. The skill uses this environment variable directly to populate the Authorization header in the local .mcp.json configuration.

How do I bootstrap a local MCP configuration if .mcp.json already exists?

To bootstrap a local MCP configuration when .mcp.json exists, the skill merges the ATLASSIAN_MCP_CREDENTIALS environment variable into the file non-destructively. This preserves your existing local settings while injecting the required Authorization header for the Atlassian integration.

Do I need to store Atlassian credentials in a specific environment variable for local MCP?

Yes, you need to store Atlassian credentials in the ATLASSIAN_MCP_CREDENTIALS environment variable for local MCP setup. The skill strictly enforces envvar storage and a fixed local scope at ./.mcp.json, avoiding hardcoded secrets or interactive credential prompts.