wirk-mcp
OfficialRelated Servers
Alternatives to wirk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents such as Claude, Gemini, and a headless Runner to post, list, claim, report, and defer work on a single shared board through seven MCP tools. Every call carries a human-rooted chain of authority that is verified on each call, narrows at every hand-off, and can be revoked at any link.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceProvides MCP tools for hybrid knowledge base search, grounded Q&A with citations, agent execution, and ticket/account lookups.-
- AlicenseBqualityCmaintenanceEnables AI agents to interact with Jira and GitHub through MCP tools, including searching, creating, commenting on, and transitioning Jira issues and listing pull requests, summarizing diffs, creating issues, and commenting on GitHub.8MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to access and manage an internal support ticket queue through MCP tools, resources, and prompts, including searching and viewing tickets, adding comments, closing tickets with confirmation, reading knowledge base articles, and viewing queue summaries over OAuth-secured Streamable HTTP.-
- AlicenseAqualityCmaintenanceEnables AI models to perform IT service management operations on Freshservice, including managing tickets, changes, problems, releases, assets, projects, and more through a set of MCP tools.362MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and humans to collaboratively manage kanban boards and Markdown documentation via MCP tools, with stable item keys, revision-safe editing, and full audit trails.MIT
TDQS
Scored across 5 tools
The tools are mostly distinct by role: query reads, write mutates, review decides proposals, show publishes a read-only view, and status gives a starting dashboard. Status, query, and show all involve reading, but their descriptions clarify different outputs and use cases.
All tools share a clear wirk_ prefix and follow a predictable second-word pattern. The names are concise and consistently snake_case.
Five tools are well-scoped for a work-item collaboration server. Each tool maps to a distinct lifecycle phase without obvious redundancy.
The surface covers reading, atomic writes, review decisions, sharing, and status, which is strong lifecycle coverage. Minor gaps remain around explicit create/delete/archive semantics, though wirk_write may cover some of these implicitly.