Your account stays yours
Connect through Nextcloud Login Flow. The bridge never asks you to paste your Nextcloud password or app password.
An open-source, tenant-isolated bridge that lets ChatGPT and Codex work with files in your own Nextcloud—without collecting your Nextcloud password.
Public hosted access opens after production OAuth validation and OpenAI review.

Designed around boundaries
The bridge does not turn a chat into an all-access cloud admin. It exposes focused tools with explicit scopes, limits, and risk metadata.
Connect through Nextcloud Login Flow. The bridge never asks you to paste your Nextcloud password or app password.
Every file path is restricted to a root you select. Parent traversal and account-root access are rejected before network access.
OAuth identifies the bridge user. Nextcloud credentials live in a separate encrypted store and are resolved only for that tenant.
Read and write tools are distinct. Delete, overwrite, move, and disconnect carry explicit risk metadata for client-side confirmation.
Extract structured checks without approving, booking, paying, transmitting, or automatically archiving an invoice.
The provider core uses WebDAV and OCS today, with clean boundaries for native MCP, CalDAV, CardDAV, and future Nextcloud apps.
Two identities, one safe path
ChatGPT and Codex authenticate to the bridge with OAuth. The bridge separately connects to Nextcloud through its official Login Flow and keeps the generated credential encrypted, tenant-bound, and outside model-visible responses.
Read the security modelNatural requests, bounded tools
The public app is designed for everyday file work, not hidden automation. Destructive actions remain visible and reviewable.
Show the files at the top level of my Nextcloud workspace.
↗Find documents with “household” in the filename.
↗Create a folder named Project Notes.
↗Review the newest invoice, but do not approve or pay it.
↗Real Nextcloud validation
WebDAV and OCS read, write, move, download, and cleanup flows passed against Nextcloud 33.0.7. Native Nextcloud MCP was not available on that instance—the standards-based fallback still completed the full smoke test.