Upvote Club MCP Coreofficial
F
licenseNot graded
qualityB
maintenanceProvides tools to interact with the Upvote.club Public API, including creating tasks, checking task status, listing platforms, and more.
39
-
upservice-mcp
by alexherbaly
Related Servers
Alternatives to upservice-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables interaction with the Upvote.club Public API for task management, including creating, deleting, and checking task status, as well as listing platforms and API reference.5-
- FlicenseAqualityDmaintenanceEnables AI models to interact with the Upsprints API for managing users, companies, projects, and tasks, including generating Software Design Documents (SDDs) from tasks via read/write tools and webhooks.5-
Upvote.club Local MCPofficial
FlicenseAqualityDmaintenanceProvides access to Upvote.club public API via stdio, enabling task creation, status checking, platform listing, and API reference queries.540-- AlicenseAqualityDmaintenanceProvides API access to a locally-hosted task management system with features for creating, updating, and organizing tasks, including support for urgency levels, effort estimates, subtasks, and bi-directional sync with Obsidian markdown files.1216MIT
- AlicenseNot gradedqualityDmaintenanceProvides a standardized interface for interacting with Unipile's tools and services through a unified API.MIT
TDQS
B3.3/5.0
Scored across 58 tools
Disambiguation2/5
The messaging tools overlap heavily: list_chat_messages vs get_chat_messages are nearly indistinguishable from their descriptions, and create_external_message vs send_channel_message vs send_chat_message blur the boundary between a channel, a room, and an external message. Outside messaging, most task/project/sprint/directory tools are clearly distinct, but the chat subset creates real misselection risk.
Naming Consistency4/5
Names overwhelmingly follow the upservice_<verb>_<noun> pattern, which is a strong and predictable convention. The main deviations are upservice_task_agreement_action (noun-first instead of verb-first) and the mixed create_/send_ verbs across the message tools, but these are minor against the overall consistency.
Tool Count1/5
58 tools is well past the 50+ threshold and is extreme for a single MCP server, even for a broad project-management API. The agent-facing surface is bloated and would be far more navigable if split into focused servers by domain (tasks, projects, directories, chat).
Completeness4/5
The server provides solid CRUD coverage for tasks, projects, sprints, tags, directories, and directory records, plus file upload/download and task workflow operations. Notable gaps include no way to discover channels/chat rooms, no remove-tasks-from-sprint operation, and no update/delete for messages, which agents may need to work around.
Maintenance
ActivityMaintained
ResponsivenessNo issues