Skip to main content
Glama
zach-snell

jtk

by zach-snell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to jtk

No user-submitted related servers found.

    Related Servers

    • bbkt

      zach-snell
      A
      license
      A
      quality
      C
      maintenance
      A Bitbucket CLI and MCP server written in Go for managing workspaces, repositories, pull requests, pipelines, issues, and source code. Supports stdio and HTTP transport.
      10
      4
      Apache 2.0

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

    • jira-mcp

      EllGree
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.
      542 npm
      MIT

    • Jira CLI MCP

      benomahony
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that wraps the Jira CLI tool, exposing Jira commands through MCP resources, tools, and prompts for AI assistant integration.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool is scoped to a distinct Jira domain (issues, projects, users, boards, worklogs, attachments, etc.), so the boundaries are clear. The only potential overlap is between searching within manage_search and listing within other tools, but the resource-specific naming prevents real ambiguity.

    Naming Consistency5/5

    All tools follow a consistent manage_<plural_noun> convention, and each tool exposes lowercase verb-style actions. This creates a predictable pattern that makes it easy to infer what each tool does.

    Tool Count5/5

    Ten tools is well-scoped for a Jira server. The count is large enough to cover distinct functional areas without becoming unwieldy, and the grouping of many actions under manage_issues keeps the surface organized.

    Completeness4/5

    Core Jira workflows are well covered: issues, projects, search, comments, attachments, worklogs, users, boards, sprints, and dev info. Minor gaps exist in version and worklog management (no create/update/delete for versions, no edit/delete for worklogs), but these are edge operations rather than critical missing workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources