Skip to main content
Glama
thamaraiselvam

Jira & Confluence MCP Server

by thamaraiselvam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Jira & Confluence MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Atlassian

      omkar9854
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for Atlassian Jira and Confluence that supports both Cloud and On-Prem/Data Center deployments. It enables AI assistants to search, create, and manage issues and pages using secure authentication methods like PAT and OAuth.
      5
      MIT

    • MCP Atlassian

      uchinx
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that integrates with Atlassian Confluence and Jira, enabling AI assistants to search, create, and update content in these platforms through natural language interactions.
      1
      MIT

    • MCP Atlassian

      saihiteesh
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables interaction with Atlassian products (Confluence and Jira), supporting both Cloud and Server/Data Center deployments for searching, creating, and managing content through natural language.
      -
    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.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool has a clearly distinct resource+action target, and the Confluence/Jira split is reinforced by consistent naming. The only mild adjacency is jira_update_issue vs jira_transition_issue, but the descriptions make the workflow-transition distinction explicit.

    Naming Consistency3/5

    Jira tools use a uniform 'jira_verb_noun' prefix pattern, but Confluence tools use a suffix form (search_confluence, get_confluence_page, add_confluence_comment), so the two families follow different conventions. Each family is internally readable, but the set as a whole mixes styles.

    Tool Count5/5

    15 tools split cleanly across two products (8 Jira, 7 Confluence) is well-scoped for a combined server. Each tool covers a distinct operation with no filler.

    Completeness4/5

    Core lifecycle is covered for both domains: search/get/create/update plus comments and transitions for Jira, and search/get/create/update/comments/versions/permissions for Confluence. Gaps remain around deletes (no Jira or Confluence delete, and comments explicitly cannot be deleted) and Jira attachment/sprint operations, but these are workable omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources