A
licenseA
qualityC
maintenanceAn MCP server that splits coding work between ChatGPT web (planning, review) and Codex CLI (implementation), enabling agentic workflows over a local repo with risk-gated execution and safety rails.
23
MIT
chrysalide-mcp
by oumar5
Related Servers
Alternatives to chrysalide-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceAn MCP server implementing Spec-Driven Development workflows for AI-agent CLIs and IDEs like Claude Code and Cursor, enabling spec-first development with automated workflow guidance and quality checks.16271 npm52MIT
- AlicenseNot gradedqualityFmaintenanceMCP server that runs Kimi K2.7-code as an autonomous coding agent inside a bubblewrap-sandboxed git worktree, returning git diffs of changes for review.MIT
- AlicenseAqualityAmaintenanceA local MCP server that delegates coding tasks to a temporary OpenCode session and returns a completion report with changed files, tool calls, cost, and the subagent's reply.1517 npm1MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables autonomous code development by pulling GitHub issues, fixing them in a sandboxed environment, running tests, opening PRs, and promoting to production upon human approval.3AGPL 3.0
- AlicenseAqualityCmaintenanceEnables MCP clients to delegate routine coding tasks to a local model in isolated git worktrees, using test results as a gate and the client as the reviewer before changes are merged.5MIT
TDQS
A3.6/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct action: start a job, check status, cancel a job, and fetch the report. The lifecycle states are clearly enumerated in descriptions (running, finished, cancelled), leaving no ambiguity about which tool to call at any point.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with a uniform prefix (chrysalide_get_status, chrysalide_get_report, chrysalide_cancel_task, chrysalide_start_task). Verbs are all action-oriented and snake_case is used consistently throughout.
Tool Count4/5
Four tools is a reasonable, focused set for a job-management server covering start, status, report, and cancellation. It's on the smaller end but each tool earns its place and the scope is appropriately narrow.
Completeness4/5
The job lifecycle is well covered: start, poll status, retrieve report, and cancel. A possible gap is the lack of a way to list historical jobs or re-fetch past reports, but the core lifecycle has no dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues