Skip to main content
Glama
bree7e

Atlassian MCP Server

by bree7e
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Atlassian MCP Server

No user-submitted related servers found.

    Related Servers

    • JIRA MCP Server

      hackdonalds
      A
      license
      B
      quality
      D
      maintenance
      Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
      6
      4 npm
      3
      MIT

    • jira-mcp

      skurekjakub
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables headless Jira Cloud automation via MCP: create issues and subtasks, read and JQL-search issues, inspect agile boards and swimlanes, move issues through workflows, and add comments and attachments.
      529 npm
      MIT

    • Jira Utilities MCP Server

      celigo
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides JIRA issue management and automation through MCP tools and standalone scripts, enabling reading, searching, analyzing, and modifying issues with batch processing and OCR capabilities.
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between Jira and Confluence tools. Potential overlap between search tools is resolved by context: jira_search_issues searches issues, confluence_search_pages searches pages, and confluence_find_pages_for_issue links issues to pages.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a product prefix and a verb_noun structure, e.g., jira_create_issue, confluence_get_page. Minor verb variation (search, list, find) is still predictable and does not create confusion.

    Tool Count5/5

    With 13 tools covering both Jira and Confluence core operations, the set is well-scoped for an Atlassian integration. Each tool addresses a meaningful operation without unnecessary bloat or duplication.

    Completeness4/5

    The server covers essential Jira issue and Confluence page workflows, including search, read, create, update, and comments. Minor gaps exist such as delete operations, Jira transitions, and Confluence page deletion, but core integration workflows are not blocked.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources