jira-dc-advops-mcp
Related Servers
Alternatives to jira-dc-advops-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides MCP integration for Atlassian Data Center products including Jira, Confluence, and Bitbucket.109MIT
- AlicenseNot gradedqualityCmaintenanceEnables local MCP-based interaction with Jira Cloud, offering tools for issues, comments, transitions, worklogs, attachments, and user lookups while addressing gaps like attachment downloads, mention notifications, and multi-step status transitions.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to search, read, and modify self-hosted Jira and Confluence Server/Data Center content through per-user authenticated REST API tools, including issues, pages, comments, workflows, boards, sprints, and custom endpoints.27MIT
- AlicenseAqualityCmaintenanceMCP server for Jira Server/Data Center that enables issue retrieval, JQL search, comment posting, and Tempo worklog queries via the atlassian-python-api.19MIT
- AlicenseAqualityFmaintenanceAn MCP server that talks directly to Jira Cloud REST API v3 using static credentials and exposes tools for discovering customfield IDs, resolving account IDs, and updating issue fields including ADF JSON.13ISC
- AlicenseNot gradedqualityCmaintenanceEnables headless Jira Cloud automation via MCP: create issues and subtasks, read and JQL-search issues, inspect agile boards and swimlanes, move issues through workflows, and add comments and attachments.708 npmMIT
TDQS
Scored across 15 tools
Tools are mostly distinct, but structure_getBoard overlaps with structure_getForest + structure_getValues, and agile_getBoardSnapshot is similar to agile_getBoardIssues. Descriptions clarify the differences well enough to prevent most misselection.
All tools follow a consistent snake_case pattern with domain prefixes (structure_, agile_) and predictable verbs (list, get, add, locate). Compound names like getBoardConfiguration and getSnapshotToFile are uniformly constructed.
15 tools sits at the upper edge of the ideal range but is justified by two coherent subdomains (Tempo Structure and Agile boards). The to-file variants add value for large payloads rather than being redundant.
The core workflows for reading structures and boards are thoroughly covered, including hierarchy, values, snapshots, and column mapping. Missing update/delete operations are acceptable given the server's read-heavy reporting focus, but there is no way to remove issues from a structure.