Sorry for the delayed response here! (I answered a similar question on Slack that was also asked back in March, but I didn’t see that this thread was asking something similar. I assumed folks in this thread were talking about existing approaches to integrating with Claude.)
I believe that MCP is a modern, cross-platform corollary to the Mac ecosystem’s AppleScript dictionaries. It’s a great standard for discovering API endpoints and calling them in a standard way. (And as a bonus, it doesn’t involve keeping track of four-byte codes.)
Because it’s associated with the AI buzz, lots of developers are integrating it. But it’s not limited to and doesn’t have to be used with AI; there’s a great opportunity to make it easy for humans to script all those apps too.
So I’m happy to see more and more apps add support for MCP, and of course we plan to support MCP in our apps at Omni as well. (Just as we’ve supported AppleScript automation, URL automation, Workflow automation, JavaScript automation, Shortcuts automation, and App Intents automation.)
I’m really curious to see what Apple plans for OS 27. All of the OmniFocus App Intents that we built for Shortcuts are also designed for use by AI systems. Apple’s previously-announced roadmap calls for those App Intents to be integrated with Apple Intelligence and Siri in a much deeper way than the current Siri integration. But a lot has changed since they announced those plans, and I could imagine them building an MCP server or CLI into the system that would automatically expose those intents for any model to use, rather than only exposing it to Siri. (In fact, I specifically suggested this at last year’s WWDC.)
Of course, Omni Automation provides an even richer JavaScript API with documented classes and methods that the latest LLMs have already demonstrated they’re pretty good at using. So one could also imagine exposing that through a CLI and having a result that’s even more powerful and efficient.
We’re now two weeks from this year’s WWDC, when we’ll get our first peek at what Apple has been working on over the past year and plans to ship in OS 27. That said, to be clear, we won’t just be hoping and waiting for Apple to solve this problem. We do want to see what they’re doing so we don’t end up doing a bunch of redundant work, but if they aren’t going to solve this soon then we will forge a solution ourselves (as we did with Omni Automation).
(We would have done so already, but with Liquid Glass, Omni Links, OmniOutliner 6, and OmniGraffle 8, we’ve had a lot of major projects on our plates this year!)