I'll be honest with you: my wife is currently the one doing the heavy lifting on our home renovation project. She's managing the Excel files, tracking the invoices, chasing the contractors, cross-referencing quotes against budget. I'm the one who's behind on everything else. And watching her work — competent, methodical, doing manually what I kept thinking should be automated — was a big part of what finally pushed a half-formed idea into an actual project.
There's a specific kind of work that lives in spreadsheets and email threads and nowhere else. Renovation budgets. Supplier quotes. Invoice tracking. Payment timelines. Most people doing this work are capable, organised people — not Excel novices. They know exactly what they're doing. They're just doing it by hand, every time, in slightly different ways, with no real safety net.
I've spent years in procurement and finance, and the pattern is the same everywhere. Excel is the connective tissue of how real work gets done. Not because people lack better tools — but because Excel is flexible, familiar, and nobody needs to request access to it. The "Excel jungle" isn't a failure of skill. It's what happens when capable people are handed a powerful tool with no automation layer underneath it.
What struck me watching my wife wasn't that she was struggling. She wasn't. It was how much of what she was doing was structurally identical to work I'd seen automated in theory — but never in practice, for regular people, in a local and trustworthy way.
The thought behind MCP Office Suite wasn't a sudden insight. It had been circling for a long time — through years of working with Excel-heavy reporting, through experimenting with Home Assistant and connected home automation, through early days of using ChatGPT and watching it evolve from a novelty into something that could actually interact with files and generate structured outputs.
What was missing for a long time was the right foundation. Browser automation was brittle. Scripts broke constantly. Nothing felt governed or trustworthy enough to hand off to. Then the Model Context Protocol arrived — a proper, structured way for AI assistants to interact with local tools through defined inputs and permissions. That was the piece that made the idea feel buildable rather than just thinkable.
A lot of the ideation and early planning happened with ChatGPT as a thinking partner — working through the shape of the problem, the scope, what a first version might look like.
Ideas are easy. Execution is where things fall apart — and I've been there before. What made this project different was using Action Worker as the delivery framework — a personal project-management tool built around epics, actions, dependencies, and evidence gates — to turn brainstorming into a programme with real governance. Instead of a pile of notes and half-finished experiments, I had structure: what's in scope, what's blocked, what needs proof before the next step.
The result is the MCP Office Automation Suite — a set of local-first Python MCP servers for Microsoft Office. The current lead package is Excel MCP, which covers the core flagship workflow: structured input → generate Excel artifact → validate workbook contract → output. Deterministic. Auditable. Reproducible.
The reason Excel comes first isn't arbitrary. It's because the Excel jungle is where most of the pain is. Generating a budget template from structured data. Validating an invoice file against a schema before it gets sent. Running the same report reliably every week without someone manually copying values between sheets. Small workflows — but for the people doing them by hand, they matter.
Outlook is next in the sequence once the Excel proof cycle closes. PowerPoint and Word are on the roadmap. But the public lead stays with Excel until there's real evidence that the flagship workflow is working.
This is not a Microsoft Copilot replacement or competitor. It doesn't try to replicate the in-app AI experience. It's not aimed at enterprise procurement at scale. It's also not finished — the renovation project that partly inspired it is still running. My wife is still tracking invoices in Excel. I'm still behind on my side of it.