A
licenseA
qualityA
maintenanceEnables interaction with Atlassian Jira and Confluence via their REST API, providing tools for searching, creating, updating, commenting, and retrieving issues, pages, projects, and spaces.
14
12 npm
MIT
Jira Product Discovery MCP
by aavaz-ai
Related Servers
Alternatives to Jira Product Discovery MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.4348 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.-
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Jira issues with full CRUD, transitions, linking, commenting, and file attachments via the Jira REST API v3.1043 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Jira and Confluence on Atlassian Cloud, supporting issue search, creation, updates, transitions, project listing, content search, page management, and comments.88 npm1MIT
- AlicenseAqualityDmaintenanceEnables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.95 npmMIT
TDQS
A4.4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool maps to a distinct HTTP method or unique action (get, post, put, patch, delete, add_attachment, list insights, create insight). Put vs patch could be confused, but descriptions clearly separate full replacement from partial updates, leaving no ambiguity.
Naming Consistency5/5
All tool names follow a consistent jira_<verb>_<object> pattern in snake_case, using clear verbs (get, post, put, patch, delete, add, list, create). The naming is uniform and predictable with no mixed casing or vague terms.
Tool Count5/5
With 8 tools, the set is well-scoped for a Jira/Product Discovery server, covering full CRUD, attachment upload, and Product Discovery insights. This falls comfortably in the ideal 3-15 range and each tool serves a distinct purpose.
Completeness4/5
Generic Jira operations are well covered via jira_get (search), post (create), put/patch (updates), and delete, including comments, worklogs, and attachments. The JPD insight tools add create and list, but lack update/delete for insights; however, generic verbs may cover some of that. The core surface is strong with minor gaps.
Maintenance
ActivityStale
ResponsivenessNo issues