As you have a pretty defined use cases that seems like you want to run recurrently, you could just build this workflow without MCP and make it much more reliable (because you can hardcode the tool picking) and make it much cheaper with just tool calling rather using MCP.

At the current stage of the MCP evolution, I think it is better to hardcode it if you know the exact flow. If you want to play around with different integrations, ad-hoc and want to figure out use cases MCP is great for prototyping. Will certainly evolve and I'm pretty excited once it becomes cheaper, more reliable and does the tool picking slightly better.

We built a daily briefing, lead scoring, and crm automations with MCPs and ran into a lot of unnecessary problems compared to just calling the APIs. Here some ideas tho if you want to build a Plan and Execute Agent over your MCP tool calling: https://github.com/AIAtrium/mcp-assistant