Skip to main content
Glama
README.md
# morpheus-mcp

Plan state management and phase gate enforcement for AI dev loops via MCP. Morpheus tracks plan progress, enforces phase gates with evidence requirements, and coordinates task lifecycle across agents.

## Part of EvoIntel

Morpheus is one server in a suite designed to work together. Each handles a different concern in the AI development loop:

| Server | Role |
|--------|------|
| **[Morpheus](https://github.com/evo-hydra/morpheus-mcp)** | Plan state & phase gate enforcement *(you are here)* |
| **[Sentinel](https://github.com/evo-hydra/sentinel)** | Persistent project intelligence — conventions, pitfalls, co-changes |
| **[Seraph](https://github.com/evo-hydra/seraph)** | Verification intelligence for AI-generated code |
| **[Niobe](https://github.com/evo-hydra/niobe)** | Runtime intelligence & log analysis |
| **[Merovingian](https://github.com/evo-hydra/merovingian)** | Cross-repo dependency tracking & contract management |
| **[Anno](https://github.com/evo-hydra/anno)** | Web content extraction via stealth browser |

Each server runs independently, but they reinforce each other. Morpheus orchestrates the dev loop. Sentinel and Seraph provide the intelligence Morpheus gates on. Niobe watches runtime. Merovingian tracks what breaks across repos.

→ [github.com/evo-hydra](https://github.com/evo-hydra)

## Install

```bash
pipx install morpheus-mcp
```

## MCP Tools

| Tool | Description |
|------|-------------|
| `morpheus_init` | Load a plan file, parse tasks, begin tracking |
| `morpheus_status` | Plan progress, task states, active phase |
| `morpheus_advance` | Advance a task through a phase gate with evidence |
| `morpheus_close` | Mark a plan as completed |

## Phase Gates

Each phase requires evidence before advancing:

| Phase | Required Evidence |
|-------|-------------------|
| CHECK | *(none)* |
| CODE | `fdmc_preflight` with 4 lenses (consistent must include `sibling_read`) |
| TEST | `build_verified` |
| GRADE | `tests_passed` |
| COMMIT | `seraph_id` (skipped if plan has `grade: false`) |
| ADVANCE | `knowledge_gate` |

## CLI

```bash
morpheus init plans/my-plan.md    # Load a plan
morpheus status                   # Show progress
morpheus advance <task-id> CHECK  # Advance a phase
morpheus close <plan-id>          # Close the plan
morpheus list                     # List all plans
```

## MCP Configuration

Add to your `.mcp.json` or `~/.claude.json`:

```json
{
  "mcpServers": {
    "morpheus": {
      "command": "morpheus-mcp",
      "args": []
    }
  }
}
```

## License

MIT

TDQS

A4.3/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a distinct purpose with clear boundaries: morpheus_advance and morpheus_advance_batch handle phase progression, morpheus_close finalizes plans, morpheus_gate_summary provides analytics, morpheus_init loads plans, morpheus_oil_change records health checks, morpheus_progress logs observations, morpheus_reflect captures gate effectiveness, morpheus_status shows current state, and morpheus_version offers introspection. No tools overlap in functionality.

Naming Consistency5/5

All tools follow a consistent 'morpheus_verb' or 'morpheus_verb_noun' pattern with snake_case throughout. The naming is predictable and readable, such as morpheus_advance, morpheus_status, and morpheus_gate_summary, with no deviations in style.

Tool Count5/5

With 10 tools, the set is well-scoped for a project management and tracking system. Each tool serves a specific role in the lifecycle of plans and tasks, from initialization to closure and analytics, with no redundant or missing operations.

Completeness5/5

The toolset provides complete coverage for the domain of plan and task management: initialization (morpheus_init), progression (morpheus_advance, morpheus_advance_batch), logging (morpheus_progress), health checks (morpheus_oil_change), analytics (morpheus_gate_summary, morpheus_reflect), status monitoring (morpheus_status), closure (morpheus_close), and introspection (morpheus_version). There are no obvious gaps in the workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues