Jira MCP
Related Servers
Alternatives to Jira MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Jira by executing commands through the Atlassian CLI. It supports searching issues with JQL, managing comments, updating statuses, and handling issue assignments through natural language.988 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables Jira integration for comprehensive issue management, board operations, time tracking, and project management through natural language.-
- FlicenseNot gradedqualityCmaintenanceEnables interaction with JIRA through the MCP interface, allowing users to manage issues, sprints, and users via natural language commands.-
- FlicenseNot gradedqualityDmaintenanceEnables Jira issue management through natural language, including viewing, searching, creating, updating, and transitioning tasks via JQL and API operations.-
- AlicenseNot gradedqualityDmaintenanceEnables querying Jira issues using JQL and creating new issues programmatically via natural language.331 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI systems to interact with JIRA through natural language, allowing users to retrieve issue details, create new tickets, search using JQL, and access project information.3-
TDQS
Scored across 3 tools
The tools have significant overlap and ambiguity, as 'get_forecast' and 'get_weather' both retrieve weather forecasts from the National Weather Service for specified locations, making them easily confused. Only 'get_alerts' has a clearly distinct purpose focused on active alerts and warnings, but the other two tools lack clear boundaries.
All tool names follow a consistent 'verb_noun' pattern with 'get_' prefix and snake_case formatting, making them predictable and readable. There are no deviations in naming conventions across the three tools.
With only 3 tools, the set feels too thin for a server named 'Jira MCP', which suggests a project management or issue-tracking domain, but the tools are all weather-related. This is an extreme mismatch between the server name and the tool scope, indicating poor appropriateness.
The tool surface is severely incomplete for the inferred domain from the server name 'Jira MCP', which should cover Jira-related operations like issues, projects, or workflows. Instead, it only provides weather data retrieval with no CRUD or lifecycle coverage for Jira, leaving obvious gaps that will cause agent failures.