jc-mcp
Related Servers
Alternatives to jc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA token-lean MCP server for Jira Cloud that enables natural language interaction with issues, comments, transitions, and more through a set of seven normalized tools, reducing token usage via field allowlists and ADF-to-Markdown conversion.2MIT
- AlicenseAqualityDmaintenanceMinimal MCP server for Jira with configurable tools to reduce token usage, starting from ~150 tokens for basic issue retrieval.1MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.71 npm4MIT
- AlicenseBqualityCmaintenanceLightweight MCP server for Jira, Confluence, and Bitbucket — read, create, and update from your AI IDE.2016 PyPIMIT
- AlicenseBqualityDmaintenance🚀 Token-efficient MCP server for Confluence. Reduces LLM costs by 76% via Markdown conversion. Supports listing, searching, and fetching pages.33MIT
TDQS
Scored across 25 tools
Most tools target a distinct resource and action, and descriptions clarify overlapping areas such as jcm_getIssues, jcm_getIssue, and jcm_searchIssues. Some update-style tools (jcm_editIssue, jcm_transitionIssue, jcm_convertIssueType, jcm_addToActiveSprint) require careful selection, but the set is generally clear.
All tools consistently use the jcm_ prefix followed by lowerCamelCase verb-first names. The verbs vary by operation (get, search, create, update, add, remove), but the overall convention is predictable throughout.
25 tools is on the heavy side, but it covers two broad domains, Jira and Confluence, with several substantial sub-areas. Each tool appears purposeful, though the surface is larger than a typical focused MCP server.
The server covers core Jira issue, comment, link, version, sprint, transition, user, and Confluence page workflows quite thoroughly. Some gaps remain, such as deleting issues/pages, editing or deleting comments, and broader board/sprint management, but core workflows are largely supported.