F
licenseNot graded
qualityA
maintenanceEnables MCP-capable clients to browse, search, and manage projects, todos, messages, card tables, documents, uploads, comments, events, and webhooks through OAuth-authenticated API calls.
-
mcp-teamline
by aroy314
Related Servers
Alternatives to mcp-teamline
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables 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 projects, todos, messages, card tables, documents, uploads, comments, webhooks, and search through OAuth-authenticated Basecamp 3 API calls.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage Basecamp 3 projects, todos, message boards, campfires, card tables, inbox forwards, documents, uploads, comments, events, webhooks, and search through OAuth-authenticated Basecamp API calls.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to browse and manage Basecamp 3 projects and resources, including todos, messages, card tables, documents, uploads, comments, events, webhooks, and search through OAuth-authenticated API calls.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP-capable clients to browse and manage Basecamp 3 projects, todos, messages, card tables, documents, uploads, and more through OAuth-authenticated API calls.-
TDQS
A3.9/5.0
Scored across 6 tools
Disambiguation4/5
Tasks and webhooks are clearly separated by the teamline_ prefix and verb. Within tasks, list/create/complete are distinct operations, though list could be confused with create if an agent overlooks the verb. Webhooks create/remove are clearly distinct.
Naming Consistency4/5
All tools follow a consistent teamline_<domain>_<verb> pattern (auth_test, tasks_list, tasks_create, tasks_complete, webhooks_create, webhooks_remove). The only minor deviation is 'auth_test' using a noun-verb inversion (test as verb) rather than 'test_auth', but it's readable and consistent in style.
Tool Count5/5
Six tools is well-scoped for a task management integration. Each tool covers a distinct operation needed for basic task lifecycle and webhook management. No redundant tools, and the count feels appropriate (within the 3-15 ideal range).
Completeness3/5
The tools cover task list, create, and complete, but lack update (e.g., edit task name, due date, assignee) and delete operations. Webhooks support create/remove but no list. A user cannot edit an existing task without recreating it, which is a notable gap in a task management API.
Maintenance
ActivityStale
ResponsivenessNo issues