Skip to main content
Glama
formonkey

jira-issue-context-mcp

by formonkey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jira-issue-context-mcp

No user-submitted related servers found.

    Related Servers

    • Jira Enterprise MCP

      w-10-m
      F
      license
      B
      quality
      B
      maintenance
      Small MCP server for connecting to enterprise Jira using a personal access token. It enables issue operations, project listing, JQL searches, and attachment handling.
      17
      -

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      60 npm
      MIT

    • Atlassian MCP Server

      varunkumar
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that enables querying and searching Atlassian Confluence pages and Jira issues through their REST APIs. Supports retrieving content by ID or URL, searching using CQL/JQL, and listing spaces and projects.
      1
      MIT

    • Work Integrations MCP

      NazarKY
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.
      408 npm
      MIT

    • jira-mcp

      ibacher
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that wraps the Jira REST API v3, enabling issue management, searching, commenting, and transitions for openmrs.atlassian.net via Basic Auth.
      1
      -
    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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion or overlap.

    Naming Consistency5/5

    With a single tool, naming is trivially consistent.

    Tool Count2/5

    A single tool for a Jira domain is insufficient; typical Jira servers have multiple tools for CRUD and search operations.

    Completeness1/5

    Only read-only context is provided; missing essential operations like listing issues, updating, or creating issues, making the surface severely incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources