@letretro/mcpofficial
A
licenseNot graded
qualityA
maintenanceEnables AI coding tools to access LetRetro retrospectives, boards, cards, and team data through MCP.
12 npm
1
MIT
TeamStorm MCP
by taaylor
Related Servers
Alternatives to TeamStorm MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to manage tasks on a local-first board via MCP, exposing task creation, updates, and queries through a thin adapter over the REST service.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage task state through MCP, including creating, updating, and tracking tasks, with support for client-side encryption and secure local credential storage.10 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access unified development tools including code generation, documentation synchronization, test case rendering, and architecture graph queries through a single MCP server.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, read, and manage tasks and projects in a personal todo system through MCP tools.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to access Tarefy tasks, internal team conversations, and public client conversations via MCP tools like get-task and login.29 npm-
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation4/5
Most tools target distinct resources and actions: task lookup, context, comments, attachments, links, workflow, and closure scheduling. The main ambiguity is between set_task_description and update_task, since both can modify the description, though the descriptions provide some guidance.
Naming Consistency5/5
All tools follow a consistent teamstorm_<verb>_<noun> snake_case pattern, with clear verbs like get, add, set, update, schedule, and cancel. This makes the toolset highly predictable and easy to navigate.
Tool Count5/5
12 tools is a well-scoped count for a task-management integration. Each tool supports a distinct part of the workflow: reading task context and related data, writing comments and updates, and managing closure scheduling.
Completeness4/5
The server covers the core workflow well: retrieving task requirements, updating task fields and descriptions, adding comments, and scheduling or canceling closure. There is no create, list, or delete task capability, but that appears outside the intended agent workflow, so the gaps are workable.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive