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 | Plan state & phase gate enforcement (you are here) |
| Sentinel | Persistent project intelligence — conventions, pitfalls, co-changes |
| Seraph | Verification intelligence for AI-generated code |
| Niobe | Runtime intelligence & log analysis |
| Merovingian | Cross-repo dependency tracking & contract management |
| 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.
Install
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
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:
{
"mcpServers": {
"morpheus": {
"command": "morpheus-mcp",
"args": []
}
}
}
License
MIT
Metadata
Release files for morpheus-mcp 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| morpheus_mcp-0.3.1.tar.gz | 49.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| morpheus_mcp-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.1 kB
Release files / morpheus_mcp-0.3.1.tar.gz
| Download URL | morpheus_mcp-0.3.1.tar.gz |
|---|---|
| Size | 49.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d3a5208632a6821876bf98cf21c0faacba0231ac32c8237d123c6cfac71df35
|
|
BLAKE2b-256 checksum How to use checksums |
f6f55810e644a6b22a9d48f133735867862ab7c49ca407ff511fac2ae4bfa4b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / morpheus_mcp-0.3.1-py3-none-any.whl
| Download URL | morpheus_mcp-0.3.1-py3-none-any.whl |
|---|---|
| Size | 33.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
124934f9437bf1e733edcc3b60118b9bf5bb4fd35777785e20377e867f79baf6
|
|
BLAKE2b-256 checksum How to use checksums |
b86f3bd9ede2fb070666c17874e7ab30479634a1a612055bffa41169efaeb80d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for morpheus-mcp 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.