What problem does it solve? Building MCP servers and Python components for the THYROX meta-framework requires consistent conventions for tool contracts, adapter layers, FAISS persistence, and subprocess safety, which are easy to get wrong without phase-by-phase guidance. ## Core Features & Use Cases - Phase-aligned guidance: Provides specific checklists for DIAGNOSE, DESIGN/SPECIFY, IMPLEMENT, and TRACK/EVALUATE phases when working on registry/mcp/*.py and bootstrap.py. - MCP server implementation order: Defines a concrete sequence from the EvoAgentX adapter layer and dataclasses to tool registration and settings.json configuration. - Safety and correctness rules: Enforces timeouts on exec_cmd/exec_python, blocks destructive command patterns, ensures FAISS index persistence, and requires idempotent bootstrap scripts. - Use Case: When adding a new MCP tool to the THYROX registry, follow the Skill to specify input/output schemas in requirements-spec.md, implement the adapter with full type hints, and verify security constraints before closing the phase. ## Quick Start Ask the AI to implement a new MCP server tool in registry/mcp following the python-mcp conventions for the THYROX framework.