Skip to main content
Glama
iljasorokin

jira-dc-advops-mcp

by iljasorokin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jira-dc-advops-mcp

No user-submitted related servers found.

    Related Servers

    • jira-mcp

      nsleader
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Jira Server/Data Center that enables issue retrieval, JQL search, comment posting, and Tempo worklog queries via the atlassian-python-api.
      19
      MIT

    • jira-api-mcp-wrapper

      jarekbird
      F
      license
      A
      quality
      F
      maintenance
      An MCP server that talks directly to Jira Cloud REST API v3 using static credentials and exposes tools for discovering customfield IDs, resolving account IDs, and updating issue fields including ADF JSON.
      13
      -

    • 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.
      408 npm
      MIT

    • gojira-mcp

      windoze95
      F
      license
      Not graded
      quality
      B
      maintenance
      Atlassian Cloud admin MCP server for project/scheme management, custom field admin, Jira automation CRUD, Assets CMDB, JSM request type/SLA/queue config, Confluence space lifecycle, and org-admin APIs, designed to complement the official Atlassian Rovo MCP.
      -
    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

    A4.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Tools are mostly distinct, but structure_getBoard overlaps with structure_getForest + structure_getValues, and agile_getBoardSnapshot is similar to agile_getBoardIssues. Descriptions clarify the differences well enough to prevent most misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with domain prefixes (structure_, agile_) and predictable verbs (list, get, add, locate). Compound names like getBoardConfiguration and getSnapshotToFile are uniformly constructed.

    Tool Count4/5

    15 tools sits at the upper edge of the ideal range but is justified by two coherent subdomains (Tempo Structure and Agile boards). The to-file variants add value for large payloads rather than being redundant.

    Completeness4/5

    The core workflows for reading structures and boards are thoroughly covered, including hierarchy, values, snapshots, and column mapping. Missing update/delete operations are acceptable given the server's read-heavy reporting focus, but there is no way to remove issues from a structure.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources