Nice, but I don't see a lot of ECMA 376 test cases. Both https://github.com/rcarmo/python-office-mcp-server and https://github.com/rcarmo/go-ooxml are ECMA 376 compliant (I made sure), because for headless generation and handling that's kind of important :)
Oh, and you're not the first, I started this a year ago. :)
> OfficeCLI is the first and best Office suite purpose-built for AI agents to read, edit, and automate Word, Excel, and PowerPoint files. Free, open-source, single binary, no Office installation required.
1. Calling Microsoft Office simply "Office" without qualification treats it like a trademark, rather than a generic term that was in use for this class of product before MS appropriated it.
2. If you're going to treat it like a trademark, don't violate it in the same sentence.
If you don't need interactive/animated features, I can absolutely recommend to have the agent build slides in HTML and convert it to PDF. Has been a game changer for me.
cool,
im working on something similar. A fine-tuned model for agents to interact with docx over MCP. they wont have to deal with OOXML.
we have a waiting list for beta-users: www.vespper.com
Feel like overnight I suddenly started seeing so much stuff and comments on here concerning generating Office documents with the LLMs. What could be driving this? Doesn't latex or similar seem like a better fit here?
cool,
im working on something similar. A fine-tuned model for agents to interact with docx over MCP. they wont have to deal with OOXML vespper.com
I went in the opposite direction and built https://smalldocs.org/, which is an office suite AI agents (and humans - including SWEs!) like to use.
I say it’s as if “Claude Code & Microsoft Office had a baby...”
Code available: https://github.com/espressoplease/smalldocs
Discord: https://discord.gg/txjATTsDaq
Sample document: https://smalldocs.org/blogs/what-is-a-smalldoc
Invoked via Claude Code by saying stuff like: “sdoc me the plan for this feature”, or “dig into our logs and sdoc me a report on our latency”