Skip to main content
Glama
panitw

jira-pm-mcp

by panitw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to jira-pm-mcp

No user-submitted related servers found.

    Related Servers

    • Jira MCP Integration

      Koveh
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.
      -

    • JIRA MCP Server

      JasserAmri
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides comprehensive access to Jira Cloud and Data Center instances for managing issues, epics, and attachments with AI-optimized data cleaning. It supports relationship tracking and dual transport modes via STDIO and Streamable HTTP.
      449 npm
      MIT

    • Jira MCP Server

      tristandistretti
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Jira API calls as tools for use with AI models like Claude, enabling project listing, board management, issue creation/deletion/status updates, and more.
      78 npm
      Apache 2.0

    • jira-mcp

      thammarongg
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.
      43
      83 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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup_project for configuration, run_sprint_audit for comprehensive sprint audit, sync_sprint_tasks for blocking task synchronization, and search_issues as an ad-hoc JQL escape hatch. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (setup_project, run_sprint_audit, sync_sprint_tasks, search_issues), making the naming predictable and easy to understand.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose as a PM monitoring assistant. Each tool serves a necessary function (setup, audit, sync, search), and the count fits comfortably within the typical 3-15 range.

    Completeness4/5

    The tool set covers the core PM workflow: configuration, audit, task synchronization, and ad-hoc queries. However, it references a 'get_sprint_health' tool that is not provided, and lacks tools for direct issue creation or manual updates, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources