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.1548 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for TickTick API enabling task management, project organization, habit tracking, and more.26 npm73MIT
- AlicenseAqualityAmaintenanceMCP server for Taskboi task management, enabling project and task operations with recurrence and priority support via the Taskboi API.163 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.898 npm1MIT
TDQS
Scored across 40 tools
Several tool boundaries require careful reading, such as share_cursor_agent vs share_cursor_agent_bitbucket, install_cursor_skills vs share_cursor_skill, and create_comment vs update_comment vs create_external_comment. Descriptions do disambiguate well, but the overlaps are numerous enough that misselection remains possible.
All tools use the runrunit_ prefix and snake_case, which is highly consistent. There are minor deviations from a strict verb_noun pattern, such as runrunit_commits_branches_prs and runrunit_assignment_play, but the naming remains predictable.
With 40 tools, the set is too large for comfortable tool selection and exceeds the typical 3-15 range. While the server spans multiple domains, the volume makes it heavy and increases the chance of choosing the wrong tool.
Core task, comment, git/PR, and Discord flows are covered, but there are notable gaps: no pause/stop tracking for assignments, no project create/update/delete, and limited Discord/Cursor lifecycle management. These gaps are workable but will cause some agent dead ends.