amulen-mcp
Related Servers
Alternatives to amulen-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to browse, search, and manage projects, todos, messages, card tables, documents, uploads, comments, events, and webhooks through OAuth-authenticated API calls.-
- AlicenseNot gradedqualityCmaintenanceEnables an authenticated owner to manage a personal task board over MCP: creating and updating tasks with project, status, assignee, and revision checks, reading ready or blocked items and recent changes, and appending reported workflow activity. It can also open an embedded workspace app in MCP Apps hosts and inspect or retry experimental board notification state.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to navigate and modify Weeek projects, boards, tasks, assignees, comments, tags, and time tracking through the Weeek API, with actions attributed to the API token owner.1358 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to read TeamStorm tasks, comments, attachments, and links, and to perform limited write operations such as adding comments and updating task names, descriptions, or statuses through MCP.153MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage Basecamp 3 projects, todos, messages, card tables, documents, uploads, and search through OAuth-authenticated API calls.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage Basecamp 3 projects, todos, messages, card tables, documents, uploads, and search through OAuth-authenticated API calls.-
TDQS
Scored across 22 tools
Tools are mostly separated cleanly by resource and action across projects, boards, tasks, attachments, checklists, comments, and identity. The main overlap is between amulen_my_tasks and amulen_list_tasks (which also supports 'mias' and 'asignado_a'), but the descriptions clarify cross-project vs board-scoped usage.
Nearly all tools follow a consistent amulen_ prefix plus verb_noun pattern (get_, list_, create_, update_, add_, delete_, upload_, download_). A few exceptions such as amulen_whoami, amulen_my_tasks, and amulen_project_dashboard break strict verb_noun form but remain readable and predictable.
At 22 tools the server is on the high end, but the domain spans projects, boards, tasks, comments, checklists, attachments, and identity, so most tools are justified. It is slightly heavy rather than excessive for the stated scope.
Core read/create/update workflows are covered, including attachment and checklist lifecycle operations. However, there are no delete operations for tasks, projects, or boards, and no member add/remove or comment edit/delete, which are notable gaps for full project management.