mcp-runrunit
Related Servers
Alternatives to mcp-runrunit
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that gives Claude access to Runrun.it tasks, projects, clients, users, boards, and more via the Runrun.it REST API v1.0, including listing, creating, updating, deleting, and time-tracking operations.-
- FlicenseNot gradedqualityCmaintenanceMCP server for the Runn API, enabling resource management and reporting through natural language.-
- AlicenseBqualityDmaintenanceMCP server for ClickUp task management, enabling task search, creation, update, deletion, workspace info retrieval, and comment management via ClickUp API v2.1525 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for TickTick API enabling task management, project organization, habit tracking, and more.19 npm73MIT
- AlicenseAqualityAmaintenanceMCP server for Taskboi task management, enabling project and task operations with recurrence and priority support via the Taskboi API.164 npmApache 2.0
- AlicenseBqualityDmaintenanceMCP server for Redmine project management, enabling tools for managing projects, issues, users, time entries, groups, memberships, versions, wiki, news, attachments, search, and Agile sprints via the Redmine REST API.893 npm1MIT
TDQS
Scored across 34 tools
Most tools map cleanly to a resource+action pair (get_task, list_projects, create_comment), and the descriptions heavily disambiguate similar operations. The main risks are near-duplicates like share_cursor_skill vs share_cursor_skill_bitbucket and discord_create_channel vs discord_get_or_create_channel, but platform suffixes and clarifying notes make the intent mostly clear.
The runrunit_ prefix and dominant verb_noun pattern provide a readable base, but the set mixes conventions: discord_list_channels, discord_send_message, assignment_play, comment_reaction, and project_detect_platform break the expected verb-first structure. Two competing patterns reduce predictability.
At 34 tools, this server is overly large and spans unrelated domains: Runrun.it task management, Cursor skill/agent sharing, Discord channel operations, PR templates, and developer suggestions. This exceeds the 25-tool threshold and feels like a monolith that should be split into focused servers.
The core Runrun.it domain is thoroughly covered with full CRUD for tasks and comments, stage transitions, workflow creation, assignment play, board stages, and task filters. Minor gaps exist outside the main domain, such as no Discord message reading/deletion and no explicit Cursor skill uninstall, but these are tangential to the primary purpose.