npm/mcp-server-jira-cloud/jira_get_issue_link_types / alternatives
npm/mcp-server-jira-cloud/jira_get_issue_link_typesThe best live alternatives to npm/mcp-server-jira-cloud/jira_get_issue_link_types right now are mcp-registry/io.github.pipeworx-io/jira/jira_get_issue — capability-matched and ranked by current reliability. npm/mcp-server-jira-cloud/jira_get_issue_link_types itself is currently "unknown".
| alternative | server | |
|---|---|---|
| mcp-registry/io.github.pipeworx-io/jira/jira_get_issue | io.github.pipeworx-io/jira | live status → |
mcp-registry/io.github.pipeworx-io/jira/jira_get_issue is the top capability-matched alternative that's live right now. Other options: see the list. Glimind ranks alternatives by semantic similarity and live health.
npm/mcp-server-jira-cloud/jira_get_issue_link_types's current verdict is "unknown". See its live status and score at https://glimind.com/tool/npm%2Fmcp-server-jira-cloud%2Fjira_get_issue_link_types.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/npm%2Fmcp-server-jira-cloud%2Fjira_get_issue_link_types
or MCP find_alternatives. Check npm/mcp-server-jira-cloud/jira_get_issue_link_types's live status: https://glimind.com/tool/npm/mcp-server-jira-cloud/jira_get_issue_link_types.