A
licenseB
qualityC
maintenanceConfluence CLI & MCP Server — dual-mode Go binary for Confluence Cloud with 7 tools, folder CRUD, page diff, and write gating.
8
1
Apache 2.0
jtk
by zach-snell
Related Servers
Alternatives to jtk
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceThe most comprehensive Azure DevOps MCP server & CLI — 13 tools, 82 actions, single Go binary.141Apache 2.0
- AlicenseAqualityBmaintenanceA Bitbucket CLI and MCP server written in Go for managing workspaces, repositories, pull requests, pipelines, issues, and source code. Supports stdio and HTTP transport.104Apache 2.0
- AlicenseNot gradedqualityBmaintenanceJira Cloud MCP server providing Jira-first tools for common workflows and full REST API coverage through a generic request tool.408MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that wraps the Jira CLI tool, exposing Jira commands through MCP resources, tools, and prompts for AI assistant integration.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.408MIT
TDQS
B3.3/5.0
Scored across 10 tools
Disambiguation5/5
Each tool is scoped to a distinct Jira domain (issues, projects, users, boards, worklogs, attachments, etc.), so the boundaries are clear. The only potential overlap is between searching within manage_search and listing within other tools, but the resource-specific naming prevents real ambiguity.
Naming Consistency5/5
All tools follow a consistent manage_<plural_noun> convention, and each tool exposes lowercase verb-style actions. This creates a predictable pattern that makes it easy to infer what each tool does.
Tool Count5/5
Ten tools is well-scoped for a Jira server. The count is large enough to cover distinct functional areas without becoming unwieldy, and the grouping of many actions under manage_issues keeps the surface organized.
Completeness4/5
Core Jira workflows are well covered: issues, projects, search, comments, attachments, worklogs, users, boards, sprints, and dev info. Minor gaps exist in version and worklog management (no create/update/delete for versions, no edit/delete for worklogs), but these are edge operations rather than critical missing workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues