Skip to main content
Glama
anands-bounteous

jira-confluence-mcp

by anands-bounteous
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to jira-confluence-mcp

No user-submitted related servers found.

    Related Servers

    • Atlassian MCP Server

      varunkumar
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that enables querying and searching Atlassian Confluence pages and Jira issues through their REST APIs. Supports retrieving content by ID or URL, searching using CQL/JQL, and listing spaces and projects.
      1
      MIT

    • jira-mcp

      PhoebusForWork
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables interaction with Atlassian products (Jira and Confluence), with additional tools for uploading attachments, embedding images, and commenting with images. It supports both Cloud and Server/Data Center deployments.
      MIT

    • Jira Cloud MCP Server

      aaronsb
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.
      195 npm
      4
      MIT

    • jira-mcp

      zhiyue
      A
      license
      B
      quality
      D
      maintenance
      MCP server providing access to JIRA data with relationship tracking, optimized payloads, and data cleaning for AI contexts. Supports both Jira Cloud and Server/Data Center.
      9
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: Jira actions target tickets, comments, fields, and attachments, while Confluence actions target pages, child pages, and search. Overlap is minor and resolved by descriptions, such as get_ticket for whole-ticket data and get_attachment for one specific attachment.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern: get_*, search_*, post_*, update_*. There are no one-word verbs, version suffixes, or mixed conventions, making the tool set predictable.

    Tool Count5/5

    Eight tools is well-scoped for a server spanning Jira and Confluence. Each tool serves a distinct purpose and none are redundant, keeping the surface compact while covering meaningful retrieval and update workflows.

    Completeness4/5

    The set supports the core investigation workflow: search and read Jira tickets, download attachments, add comments, update fields, and search/read Confluence pages. Missing issue creation, issue deletion, and Confluence write operations are notable as general CRUD gaps, but they appear to be intentionally outside the workflow described by this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources