Does eMoney have an MCP server?

Planning data has a particular failure mode worth naming. An eMoney plan is a model with assumptions behind it, not a set of facts, and an assistant reading plan outputs through a bridge will not reliably carry those assumptions with the numbers. A projected balance pulled into a client email without its assumptions is a compliance problem, not just an accuracy one.

Treat anything an agent returns from a planning system as a draft that needs checking against the plan itself. Start read-only, and confirm what the bridge exposes before pointing it at a client deliverable.