Thoughts on MCP for Cloudflare OS (allow external agents to control CF:OS)

[cdolan-personal]

Love CFOS. Also a big Grokbot user!

Would love to be able to control my CF:OS from an agent. In terms of drafting new workspaces/gadgets, controlling access for my team, and so on

What does the community think of this type of usage pattern? Does it make sense for CF:OS to bundle an MCP 2.0 capability so our "Chief of Staff" agents (ClaudeCode, GrokBot, Codex, etc) can influence our CF:OS installs?

This would also permit gadget creation using developer-focused context (like our Cursor Cloud environments)

[twinprime19]

Honestly, I'm not sure it makes sense to expose an MCP service here just so external AIs can drive the platform. Since the whole system is designed primarily for human interaction, having external agents (like Hermes) drive it from the outside feels a bit backward—at least for our use case. Definitely open to being corrected if I'm missing a key scenario, though!

For context on where I'm coming from: we're replacing a fairly dated Dify setup with CF-OS. In our deployment, we build MCPs into our internal apps so users working inside CF-OS can reach external systems, rather than the other way around.

That said, the Gadget and Blueprint concept is super solid. We're actually replacing several internal apps with a single Blueprint. Our invoice and PO processing (with AI OCR) used to live in a standalone customer-facing app, but moving it to CF-OS via Gadget → Blueprint → Publish/Promote gives us the whole pipeline in one place.

Overall, those initial Blueprints (Docs, Slides, Sheets) are impressively capable—the "OS" name is definitely earned!