What is the role of the MCP server in the HungryTraveler agent architecture?

In HungryTraveler, the MCP server exposes previously built Langflow flows, such as HealthyChef and HistoryTravelBuddy, as discoverable tools that the parent agent can invoke as needed. This allows the HungryTraveler supervisor agent to reuse existing child-agent abilities and combine them for a new, more complex task without hand-built point-to-point integrations.

The HungryTraveler agent acts as a parent or supervisor agent, while its child agents are connected through an MCP server that exposes their abilities as tools. Each flow in the Langflow project becomes a tool on the MCP server, and the HungryTraveler agent can discover and call those tools based on context. For example, the HealthyChef flow generates recipes and the HistoryTravelBuddy flow creates travel itineraries. The MCP server also sends each tool's description to the agent, telling it exactly when to use that tool, which helps the LLM choose the right one. Meanwhile, the email-sending capability is handled by a separate Gmail component connected directly to the HungryTraveler agent, not through MCP.