Actually, while MCP is a great direction for standardizing context, the "special sauce" of Ego isn't the context-passing itself, but the proprietary engine that uses that context to dynamically generate prompts from a deep personality model.
For the MVP, I had to build the custom state handler to prove out that core persona logic first. Long-term, I'd love for Ego to accept context from standard protocols like MCP—it would make the engine even more versatile.
You're definitely right for now, MCP is great for 'stuffing context'.
However, the long-term goal of this framework is to make the persona itself dynamic. It's designed to use that context to subtly update a persona's core personality traits over time, creating a more 'life-like' evolving 'virtual soul'.
The cherry-on-top is framing it all as a 'Persona-as-a-Service' API to make the dev workflow straightforward but powerful. It's not for every application, but for anything that needs real character depth - like in gaming or advanced assistants - the goal is to make it simple for any developer to create those deeper, more meaningful interactions that are typically hard to get right.
For the MVP, I had to build the custom state handler to prove out that core persona logic first. Long-term, I'd love for Ego to accept context from standard protocols like MCP—it would make the engine even more versatile.
Appreciate the sharp question!