F
licenseA
qualityC
maintenanceMCP server that enables AI assistants to run multi-step agent pipelines (e.g., Issue Analyst → Code Writer → Test Runner → PR Opener) from conversations, with support for Devin, shell, Python, and HTTP agents.
7
-
emergent-mcp
by Nextahalli
Related Servers
Alternatives to emergent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to start, monitor, and stop background processes like dev servers, builds, and tests, with a web dashboard.7 npm2MIT
- FlicenseAqualityDmaintenanceMCP server for creating, monitoring, and managing Devin AI sessions.41-
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets a coding agent turn a plain-language idea into a real, shareable product — creating the project and data model, serving live API endpoints, deploying custom endpoints and server-side functions, and reading request and function logs. It handles sign-up, OAuth-backed access, and OpenAPI spec generation so people can open, sign into, and use the app the agent builds.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that turns any running web app into demo videos, interactive walkthroughs, and marketing captures via one command. Enables AI agents to show their work with regenerated demos on every PR.9 npm6MIT
- AlicenseAqualityDmaintenanceAn MCP server for managing and executing AI agents on the Spaceship AI platform directly from clients like Claude Code and Cursor. It provides comprehensive tools for agent lifecycle management, including creation, execution, and real-time monitoring of run statuses and logs.161MIT
TDQS
A3.6/5.0
Scored across 11 tools
Disambiguation3/5
Most workflow tools (create, wait, respond, wake) are clearly separated, but get_credits and credit_summary both surface credit balance information, and get_preview duplicates the preview URL already available from get_project and list_projects. Descriptions help clarify the differences, but the boundaries are not fully crisp.
Naming Consistency4/5
Tools share an emergent_ prefix and generally follow verb_noun naming such as create_project, list_projects, wait_for_build, and wake_environment. The pattern is slightly weakened by emergent_credit_summary, which lacks a verb, and emergent_screenshot_preview, where screenshot is used awkwardly as a verb, but the overall convention is predictable.
Tool Count4/5
With 11 tools, the server stays within a reasonable scope and covers the main project lifecycle. The count is slightly inflated by redundant helpers like credit_summary and get_preview, but it is not overwhelming or insufficient.
Completeness3/5
The server covers the core build workflow well: create, monitor/wait, respond to HITL questions, wake environments, preview, screenshot, and check credits. It lacks obvious lifecycle operations like canceling or stopping a build and deleting or archiving a project, and discover_features suggests the API surface has gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues