Murena Workspace already speaks open standards — CalDAV, CardDAV, WebDAV, IMAP/SMTP — which is why third-party apps can plug in without a proprietary API. I’d like to propose one more standard interface: an MCP (Model Context Protocol) server.
MCP is an open protocol (not Anthropic-only — it’s being adopted across the AI assistant ecosystem) that lets an assistant read and act on a service’s data through a defined, permissioned set of tools, instead of scraping. Claude is the most visible example, but any MCP-compatible assistant would work.
Why it fits Murena: the platform’s whole pitch is “your data, your control, no vendor lock-in.” An official MCP server keeps that promise — opt-in, scoped, revocable, and not tied to one AI vendor. Better that story comes from Murena than from a random unmaintained community script.
What it would enable (with explicit permission):
-
Triage email via natural language instead of hunting through folders
-
Query/manage Calendar events, including recurring ones
-
Look up Contacts
-
Search Files
Not asking for: Murena to bundle or promote any AI product, or for anything to read data by default. Strictly opt-in and revocable, same trust model as an app password today.
Prior art: community MCP servers already exist for vanilla Nextcloud (Calendar, Contacts, Files, Notes over DAV/WebDAV). Since Murena Workspace is a Nextcloud fork, this may be closer to “adopt and officially support” than “build from zero.”
Curious if others here would use this, and whether anyone from the team can weigh in on feasibility. Happy to help test against a real Workspace account.