Skip to main content
Glama
jarekbird

jira-api-mcp-wrapper

by jarekbird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jira-api-mcp-wrapper

No user-submitted related servers found.

    Related Servers

    • jira-mcp

      LesterAJohn
      A
      license
      Not graded
      quality
      B
      maintenance
      Jira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.
      408 npm
      MIT

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

    • MCP Jira Server

      edrich13
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It enables users to perform CRUD operations on issues, search with JQL, manage comments, and list projects through the Jira REST API.
      12
      342 npm
      13
      MIT

    • jiraxmcp

      vaibhavpandeyvpz
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with Jira Cloud, providing tools for issues, search, agile boards, comments, links, attachments, and webhook notifications.
      8 npm
      2
      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.8/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action on Jira resources. Single and bulk operations are clearly separated, and user-related tools (search_users vs resolve_user_account_id) have distinct purposes. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent 'jira_verb_noun' pattern using snake_case. Verbs are uniform (add, bulk_create, bulk_edit, create, get, list, resolve, search, transition, update), and bulk operations are prefixed with 'bulk_'. The naming is predictable and easy to understand.

    Tool Count5/5

    With 13 tools, the server covers core Jira issue operations without being overwhelming. The number is well within the ideal range (3-15) and each tool addresses a specific need, from CRUD to searching and user resolution.

    Completeness4/5

    The tool surface covers creation (single and bulk), reading, updating, commenting, searching, and transitions. Missing delete functionality is a notable gap, but the set is sufficient for most issue management workflows. Overall, it is well-scoped for its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources