Skip to main content
Glama
nianyi778

jira-dev-mcp

by nianyi778
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to jira-dev-mcp

No user-submitted related servers found.

    Related Servers

    • Work Integrations MCP

      NazarKY
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.
      542 npm
      MIT

    • Jira Enterprise MCP

      w-10-m
      F
      license
      B
      quality
      D
      maintenance
      Small MCP server for connecting to enterprise Jira using a personal access token. It enables issue operations, project listing, JQL searches, and attachment handling.
      17
      -

    • jira-mcp

      ibacher
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that wraps the Jira REST API v3, enabling issue management, searching, commenting, and transitions for openmrs.atlassian.net via Basic Auth.
      1
      -

    • 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
    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/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose. The closest pair, jira_read_task and jira_analyze_task, is explicitly disambiguated: one is data-only, the other is a full workflow. Downloading single vs all attachments is also clearly distinguished.

    Naming Consistency4/5

    All tools follow a jira_verb_noun pattern except jira_my_tasks, which breaks the convention by using a possessive adjective instead of a verb. Otherwise, naming is highly consistent and predictable.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a Jira dev integration. Each tool satisfies a distinct need, from project path mapping to comments, search, attachments, and a comprehensive analysis workflow.

    Completeness4/5

    The tool surface covers core read, search, comment, attachment, and workflow-driven analysis. Minor gaps exist—no issue creation, status transition, or assignment modification—but these are outside the apparent focus on investigation and commenting.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources