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.-
- 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.-
- AlicenseAqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables an AI to perform customer support workflows by looking up customers, retrieving orders, and creating support tickets through MCP tools.1 npmX11 no permit persons clause
TDQS
Scored across 5 tools
Each tool has a fairly distinct role: status is a read-only overview, query is targeted fetch/list/search, write mutates, review handles governance, show publishes a page. status and query both read, which creates some mild overlap, but the 'start here' framing and query's specificity keep them separable.
All tools follow a clean wirk_<verb> snake_case pattern with no style mixing. The only minor quirk is that 'status' is a noun while the rest are verbs, but the prefix-and-shape convention is fully consistent.
Five tools is well-scoped for a work-coordination server, with each mapping to a distinct lifecycle stage (overview, read, mutate, review, publish). Nothing feels redundant or missing at the count level.
Read (status/query), mutate (write handles create/update/link atomically), and governance (review) are all covered, giving a coherent lifecycle. The notable gap is wirk_show, which is admitted to be non-functional ('views_unavailable'), leaving a dead end in the surface.