Skip to main content
Glama
MichalOsadowski

jira-mcp-scoped

by MichalOsadowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to jira-mcp-scoped

No user-submitted related servers found.

    Related Servers

    • jira-mcp-server

      Hopcos
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready MCP server enabling AI assistants to interact with Jira projects, issues, sprints, users, attachments, and worklogs via natural language, with support for both local stdio and remote HTTP transports, dual authentication methods, and enterprise-grade security controls.
      2
      Apache 2.0

    • mcp-jira-stdio

      freema
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Jira integration with stdio transport. Enables reading, writing, and managing Jira issues and projects directly from Claude Desktop. Supports issue creation, updates, comments, JQL search, and project management.
      23
      475 npm
      14
      MIT

    • jira-mcp

      Pandacli
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.
      MIT

    • Jira MCP Server

      sthirugn
      A
      license
      Not graded
      quality
      D
      maintenance
      A clean and focused Model Context Protocol (MCP) server that provides seamless integration between AI assistants and Jira, enabling natural language interaction with your Jira projects, issues, and workflows.
      5
      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.9/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: fetching, creating, updating, transitioning, assigning, commenting, downloading attachments, listing sprints, and searching users. Even the two sprint-listing tools are clearly differentiated by assignee filter.

    Naming Consistency4/5

    All tools use a consistent jira_verb_noun pattern in snake_case. Minor verb variations exist (fetch vs get vs list vs search) but each verb is appropriate for its action and the pattern remains predictable.

    Tool Count5/5

    12 tools is a well-scoped number for a Jira MCP server. Each tool covers a distinct Jira operation without bloat, and the set feels comprehensive for the intended scope.

    Completeness4/5

    The tool set covers the core issue lifecycle (create, fetch, update, transition), assignment, comments, attachments (download only), sprint views, and user search. Missing issue search and attachment upload are notable gaps but not critical for a scoped server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources