Integrated Atlassian Bridge for MCP (Authored by phuc-nt)

Novelties in Build 2.1.1 🌟

• Comprehensive internal restructuring to harmonize tool/resource schema; legacy content-metadata artifact completely retired, its data now consolidated within the primary page resource.
• Introduction of a new developer manual simplifying codebase extension and upkeep.
• Enhanced adherence to the contemporary MCP SDK, resulting in bolstered security posture, improved system scalability, and greater long-term maintainability.
• Path definitions in docs/introduction/resources-and-tools.md updated to eliminate all defunct references to content-metadata.

👉 Review the comprehensive REVISION LOG for exhaustive specifics.

What's New in Build 2.0.1 🎊

The Atlassian Integration Hub (v2.0.1) introduces a substantial augmentation of functional scope and operational depth!

• API Modernization: Now utilizing the most recent Atlassian endpoint specifications (Jira API v3, Confluence API v2).
• Capability Expansion: Feature set has ballooned from 21 distinct functions to 48, encompassing sophisticated Jira and Confluence maneuvers.
• Agile Lifecycle Mastery: Full support for Scrum and general Agile process management.
• Advanced Confluence Utilities: Functionality covering page version control, digital asset handling (attachments), and thread management (comments).
• Registry Stabilization: Resolved reported anomalies concerning redundant resource instantiation, leading to a more robust operational foundation.
• Documentation Overhaul: Launched a new, in-depth documentation series elucidating the core MCP architecture and resource/tool development paradigms.

For a complete synopsis of alterations, enhancements, and defect resolutions, consult the REVISION LOG.

Conceptual Foundation

The Atlassian Integration Bridge (phuc-nt) functions as a Model Context Protocol (MCP) endpoint, bridging intelligent entities such as Cline, Claude Desktop, or Cursor directly to Atlassian Jira and Confluence ecosystems, permitting data retrieval and operational execution via a standardized communication protocol.

Note: While engineered primarily for seamless integration with Cline, this server strictly adheres to the MCP specification and is compatible with any conforming client implementation.

• Core Capabilities:
• Establishes connectivity between AI processing units and Atlassian Jira/Confluence environments.
• Provides dual access modes: Resources (for observational queries) and Tools (for transactional modifications).
• Simple onboarding into the Cline AI ecosystem via the MCP Registry.
• Employs a local-first architectural paradigm suited for isolated development settings.
• Optimized communication pathway specifically for the Cline AI assistant ecosystem.

Rationale for Creation

As a software engineer frequently navigating Jira and Confluence, I frequently experienced significant cognitive load and time loss jumping between interfaces. Despite their robust feature sets, I desired a frictionless method to interact with these systems, minimizing context switching during periods of focused work.

The advent of AI Agents and the Model Context Protocol (MCP) provided the ideal mechanism. I immediately perceived the potential to link Jira and Confluence (with future aspirations for Slack, GitHub, Calendar integration, etc.) directly into my automated workflows.

This initiative began as an educational exercise in mastering MCP principles and Agent interaction, with the hope that it matures into an indispensable asset for professionals who interact with the Atlassian suite on a daily basis.

Operational Topology

graph TD
    AI[AI Processing Unit] <--> MCP[Integrated Atlassian Bridge]
    MCP <--> JiraAPI[Jira REST Endpoints]
    MCP <--> ConfAPI[Confluence REST Endpoints]

    subgraph "MCP Bridge Core"
        Resources[Read-Only Artifacts] 
        Tools[Actionable Functions]
    end

    Resources --> JiraRes[Jira Components<br/>Tickets, Projects, Users]
    Resources --> ConfRes[Confluence Components<br/>Workspaces, Documents]
    Tools --> JiraTools[Jira Functions<br/>Creation, Modification, Status Change]
    Tools --> ConfTools[Confluence Functions<br/>Document drafting, Note insertion]

Deployment and Configuration

For exhaustive directives on initiating operation and system preparation, consult our dedicated setup dossier for AI clients. This document is specifically structured for consumption by AI/LLM assistants like Cline to facilitate automated deployment.

Guidance for Cline Users: The setup dossier (llms-install.md) is tailored for Cline's execution parsing. You may simply instruct Cline to "Initiate setup for Integrated Atlassian Bridge (by phuc-nt)" and it should parse the steps to configure the environment sequentially.

The dossier encompasses: - Necessary preliminary conditions and system specifications. - Step-by-step initialization routine for Node.js environments. - Procedures for linking the Cline AI assistant to the Atlassian Bridge. - Acquisition and deployment of necessary Atlassian credential tokens. - Security advisories and optimal configuration practices.

Automated Installation via Smithery

To deploy the Atlassian Integration Bridge automatically for Claude Desktop using Smithery:

npx -y @smithery/cli install @phuc-nt/mcp-atlassian-server --client claude

Feature Catalogue

The Integrated Atlassian Bridge empowers AI assistants (e.g., Cline, Claude Desktop, Cursor...) to access and govern Jira & Confluence data through a comprehensive feature set, categorized for clarity:

Jira Operations

• Ticket Lifecycle Management
• Visualization, comprehensive search, and structured filtering of tickets.
• Ticket generation, modification, status progression, and ownership assignment.

• Backlog placement, sprint inclusion, and priority ordering.

• Project Oversight

• Retrieval of project listings, detailed project metadata, and role assignments.

• Agile Board & Iteration Control

• Inspection of boards, configuration parameters, associated tickets, and active sprints.

• Initiation, commencement, and finalization of development iterations (sprints).

• Query Filtering System

• Viewing, authoring, modifying, and retiring saved search filters.

• Dashboard & Widget Management

• Viewing existing information displays (dashboards) and their constituent widgets.
• Creation and updating of dashboard layouts.

• Dynamic inclusion or exclusion of widgets on display surfaces.

• Personnel Identification

• Retrieving user profiles, lists of assignable personnel, and users mapped to specific project roles.

Confluence Operations

• Workspace Administration

• Listing available workspaces, retrieving workspace specifications, and mapping contained documents.

• Document Management

• Viewing, searching, retrieving comprehensive details for pages, hierarchical children, navigational paths, associated files, and historical revisions.

• Document creation, modification, title alteration, and deletion.

• Annotation Management

• Reviewing, appending, updating, and erasing annotations linked to specific pages.

For an exhaustive technical specification of every supported function, artifact, and tool, consult: docs/introduction/resources-and-tools.md

---

Interaction Protocol Diagram

sequenceDiagram
    participant User
    participant Cline as Cline Agent
    participant MCP as Integration Bridge
    participant Atlassian as Atlassian Endpoints

    User->>Cline: "Locate all assignments pending for me"
    Cline->>MCP: Query artifact jira://tickets
    MCP->>Atlassian: REST Call (Authenticated)
    Atlassian->>MCP: Response Payload (JSON)
    MCP->>Cline: Standardized MCP Artifact
    Cline->>User: "I have located these items..."

    User->>Cline: "Draft a new report regarding login failure"
    Cline->>MCP: Invoke createTicket Tool
    MCP->>Atlassian: POST /rest/api/3/ticket
    Atlassian->>MCP: Confirmation Data (New Ticket ID)
    MCP->>Cline: Operation Success Confirmation
    Cline->>User: "Ticket ID DEMO-123 successfully generated"

Security Advisory

• The operational scope of your credential token mirrors that of the originating user account.
• Strict prohibition on dissemination of your token to unverified third parties.
• Exercise prudence when instructing Language Models to parse configuration files that may embed your token.
• Refer to comprehensive security protocols detailed in llms-install.md

Collaboration and Assistance

• Support development efforts by submitting Issues or initiating Pull Requests on the GitHub repository.
• Engage with the MCP/Cline user collective for auxiliary troubleshooting support.

WIKIPEDIA: Enterprise management utilities encompass the totality of systems, software solutions, governance frameworks, computational methodologies, etc., utilized by organizations to successfully navigate dynamic market conditions, maintain competitive advantage, and elevate overall corporate effectiveness.

== Conceptual Framework == Tools are typically segmented according to departmental function, allowing classification across various management dimensions: e.g., forecasting tools, procedural governance tools, archival systems, personnel management utilities, assessment engines, oversight mechanisms, etc. A functional categorization might include:

Utilities for capturing and validating transactional data across any organizational unit. Software utilized for auditing and refining core operational sequences. Systems dedicated to data aggregation and strategic deliberation. Modern management applications have undergone radical evolution over the past decade, driven by rapid technological advancement, making the optimal selection of business tools for any given scenario challenging. This complexity stems from the perpetual drive toward cost minimization and sales maximization, coupled with the imperative to deeply understand client requirements and deliver requisite products precisely as demanded. In this environment, leadership should adopt a strategic perspective on enterprise utilities rather than defaulting to the newest market offering. Over-reliance on unadapted tools often results in systemic instability. Business management utilities demand careful selection followed by rigorous tailoring to the specific organizational mandate, not the reverse.

== Predominant Selections == In a 2013 global census conducted by Bain & Company, the usage patterns of business utilities worldwide were mapped. These selections reflect regional needs calibrated against prevailing market conditions and economic downturns. The top ten categories identified were:

Strategic planning mechanisms Client relationship management suites Personnel satisfaction assessment tools Competitive comparison techniques Performance measurement frameworks (Balanced Scorecard) Identification of core organizational competencies Strategic divestiture/outsourcing practices Organizational transition management programs Logistics and procurement chain governance Articulating organizational purpose and aspiration statements Market segmentation analysis Comprehensive quality assurance methodologies

== Business Software Applications == Software, defined as a suite of computational programs employed by personnel to execute diverse corporate functions, is termed business software (or an enterprise application). These applications aim to enhance productivity metrics, precisely measure performance indicators, and accurately execute various company tasks. This lineage began with rudimentary Management Information Systems, progressed to comprehensive Enterprise Resource Planning suites, integrated Customer Relationship Management capabilities, and has now transitioned into the realm of cloud-based enterprise management platforms. Although a demonstrable link exists between Information Technology investment and organizational outcomes, two factors are critical determinants of realized value: the efficacy of the deployment process and the judicious selection and subsequent customization of the chosen utilities.