mergestorm-mcp
OfficialRelated Servers
Alternatives to mergestorm-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceA single STDIO MCP server that provides 48 tools for browser and Chrome DevTools automation, HTTP requests, SQL and MongoDB operations, GitBook, system intelligence, disk management, web search, local transcription, and Ollama delegation, plus runtime connection to external auth-free MCP servers.1MIT
- AlicenseNot gradedqualityAmaintenanceEquips AI assistants and MCP-compatible clients with software development tools for deep research, requirements and PRD generation, user stories, task lists, codebase mapping, context curation, and full-stack project scaffolding. It also runs multi-step workflows and AI-native task management over stdio or SSE transports.42 npmMIT
- AlicenseNot gradedqualityDmaintenanceA unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.GPL 3.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.7 npm4MIT
TDQS
Scored across 37 tools
Domains (reviews, stacks, queue, settings, memory, web) are mostly separable, but within reviews and stacks there is real overlap: review_wait, review_wait_pr, review_list and review_submit all traffic in 'review jobs/envelopes', and stack_status and stack_wait return nearly identical blocker/attention semantics. The very long descriptions do disambiguate read-vs-wait and local-vs-PR, but an agent can easily pick the wrong wait/status variant.
All names are snake_case, but ordering is inconsistent even within one domain: review_list/review_submit/review_wait mix noun_verb and verb_noun, as do stack_list vs stack_publish and cyclone_job vs cyclone_start. Bare nouns (credits, whoami, remember) and verb-first names (get_memory_mode, set_memory_mode, read_web_page) sit alongside verb_noun everywhere.
37 tools is heavy for a single MCP surface, even a broad platform one; reviews alone contribute eight and stacks/queue contribute about ten. Several near-duplicates (stack_status vs stack_wait, review_wait vs review_wait_pr, local vs repo settings) inflate the count beyond what the workflow needs.
Coverage is broad: review submit/wait/start/stop/dismiss, stack adopt/list/publish/status/set/restack/enqueue/wait, queue status, account and repo settings, memory CRUD plus mode, and web search/read. Gaps are minor but real: no stack deletion/leave, no queue cancel, no cancel for local review jobs, and issue handling is limited to create plus approval wait.