# Install mcp-atlassian with Homebrew MCP server for Atlassian tools (Confluence, Jira). Version 0.23.0 via Homebrew; verified 2026-07-19. ## Install ```sh sudo av install brew:mcp-atlassian ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install mcp-atlassian ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:mcp-atlassian - **Package manager:** Homebrew - **Version:** 0.23.0 - **Source summary:** MCP server for Atlassian tools (Confluence, Jira) - **Homepage:** - **Repository:** - **Last updated:** 2026-07-19T08:32:00Z - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - mcp-atlassian (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.23.0 ## Project history and usage MCP Atlassian is a Model Context Protocol server for Jira and Confluence. Its official README describes support for Atlassian Cloud and Server/Data Center deployments and presents it as a bridge between MCP-compatible AI clients and Atlassian work data. ### Project history The repository was created in December 2024, shortly after the Model Context Protocol ecosystem began expanding around local tool servers. The project publishes dedicated documentation at mcp-atlassian.soomiles.com as well as an llms.txt and llms-full.txt documentation surface. The README documents uvx, Docker, pip, and source installation paths, along with environment-variable configuration for Jira and Confluence URLs, usernames, API tokens, and personal access tokens. ### Adoption history By July 2026, official GitHub metadata showed thousands of stars and more than a thousand forks, unusually high visibility for a narrowly scoped integration server. The supplied package facts list Homebrew packaging, while the README also advertises PyPI version and download badges. The project is part of the practical MCP server wave: teams want AI assistants to search tickets, inspect Confluence pages, and create or update Jira issues without bespoke integrations in every client. ### How it is used The quick start has users create an Atlassian API token, add an mcp-atlassian command to an MCP client configuration, and pass Jira and Confluence connection details through environment variables. Documented use cases include searching Jira with JQL, fetching issues, creating and updating issues, searching Confluence with CQL, reading pages, creating pages, and adding comments. ### Why package nerds care For package managers, mcp-atlassian is significant because it packages a workplace integration as a local MCP server rather than as a SaaS connector. The value is in making a complex enterprise API surface installable as a command. ### Timeline - 2024-12: GitHub repository created. - 2025-2026: Dedicated documentation site and llms.txt documentation surfaces maintained. - 2026-04: v0.21.1 published on GitHub releases. - 2026-07: Repository metadata showed high star and fork counts for an MCP integration server. ### Related projects - Related projects include other MCP servers for developer and workplace systems, plus the broader Model Context Protocol specification documented at modelcontextprotocol.io. ### Sources - - - - - - - source_facts.package-manager ## Security Notes No matching local secret-handling manifest was found for mcp-atlassian. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Combined YAML source View the package source record on GitHub. [combined/mcp-atlassian.yml](https://github.com/automic-vault/db/blob/main/combined/mcp-atlassian.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated package history - pkgdb category and tag curation