mcp-atlassian-extended

What this does

mcp-atlassian-extended exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

JIRA_URL
JIRA_USERNAME
JIRA_API_TOKEN
JIRA_PAT
CONFLUENCE_URL
CONFLUENCE_USERNAME
CONFLUENCE_API_TOKEN
CONFLUENCE_PAT
MCP_READ_ONLY
ATLASSIAN_READ_ONLY
ATLASSIAN_HTTP_BEARER_TOKEN
ATLASSIAN_UPLOAD_DIR
ATLASSIAN_DOWNLOAD_DIR

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install mcp-atlassian-extended?

Run the Claude Code command in the install section to add mcp-atlassian-extended to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with mcp-atlassian-extended?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to mcp-atlassian-extended as well.

Does mcp-atlassian-extended need an API key?

Yes. Before it can run, set these environment variables: JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PAT, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN, CONFLUENCE_PAT, MCP_READ_ONLY, ATLASSIAN_READ_ONLY, ATLASSIAN_HTTP_BEARER_TOKEN, ATLASSIAN_UPLOAD_DIR, ATLASSIAN_DOWNLOAD_DIR. They go in the env block of your MCP config.