Skip to main content
Glama
jgonzalezar

MCP Issue Tracker

by jgonzalezar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MCP Issue Tracker

No user-submitted related servers found.

    Related Servers

    • mock-jira

      techindicium
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with a mock JIRA-shaped issue tracker through MCP tools for managing projects, issues, and users.
      -

    • yandex-tracker-mcp

      brekhov-ilya
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.
      21 npm
      1
      MIT

    • JIRA MCP Server

      hackdonalds
      A
      license
      B
      quality
      D
      maintenance
      Provides tools for AI assistants to interact with JIRA APIs, enabling them to read, create, update, and manage JIRA issues through standardized MCP tools.
      6
      4 npm
      3
      MIT

    • issuehub

      tya5
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides issue tracking tools for Jira, Redmine, GitHub, and GitLab via the Model Context Protocol, enabling agents to search, fetch, sync, and manage issues through natural language.
      MIT

    • MCP JIRA Server

      Warzuponus
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.
      10
      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

    B3.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose: ping for health, and the remaining five tools map cleanly to list/get/create/update/delete operations on issues. There is no overlap or likely misselection between tools.

    Naming Consistency5/5

    All issue-specific tools follow a consistent verb_noun pattern (list_issues, get_issue, delete_issue, create_issue, update_issue). The only exception is ping, which is a conventional standalone health-check name and does not undermine the pattern.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a small issue tracker MCP server. Every tool earns its place: five cover the issue lifecycle and one verifies server availability.

    Completeness5/5

    The tool surface provides full CRUD coverage for issues, including listing, retrieving, creating, updating, and deleting. No core lifecycle operation is missing for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources