EasyTopic MCP Server
OfficialRelated Servers
Alternatives to EasyTopic MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables agents to read and drive a local-first Kanban board for issue tracking, allowing them to list, create, update, and resolve issues from Claude Code sessions.7 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables managing GitHub Projects v2 boards through Claude Code and Codex, including project and item administration, field updates, sprint boards, epic rollups, and desired-state planning.-
- AlicenseAqualityBmaintenanceEnables Claude Code to control a Planka 2.x board via 15 MCP tools, with writes re-read and verified so reported success matches the board, plus an optional workflow that turns the board into durable agent memory.1552 npm2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Kanban board MCP server and Claude Code plugin that allows AI agent teams to create, track, and manage tasks through a structured workflow. It features a web UI for real-time status monitoring and enables users to review, approve, or reject task submissions.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Kanban tasks, boards, teams, and checklists via natural language, with full CRUD operations and live updates.127 npmMIT
- FlicenseBqualityDmaintenanceEnables Claude to automate project management on DutyHub, including tasks, sprints, and comments.16-
TDQS
Scored across 11 tools
Tools are clearly separated into topic management and documentation project management groups, with each tool having a distinct purpose (list vs get vs add vs write vs transition vs create). No overlapping functionalities.
All tools follow the 'easytopic_verb_noun' pattern with consistent verbs (list, get, add, write, transition, create). The only outlier is 'whoami', which is a standard authentication term and fits the pattern.
With 11 tools covering two main domains (topic management and documentation projects), the number is well-scoped. Each tool serves a necessary role without redundancy.
Significant gaps exist: no create_topic or delete_topic for topic management, and no delete_doc_page for documentation. Updates to custom fields beyond the plan field are missing. However, core workflows (list, get, update status, add comments, and documentation CRUD for creation/reading/updating) are covered.