Nextcloud ChatGPT Bridge
The server is a stateless MCP bridge that lets ChatGPT/Codex interact with a user's Nextcloud workspace through OAuth, with tenant-isolated, root-bound file and account tools.
Inspect Nextcloud: get capabilities, app inventory, search providers, and probe for native Nextcloud MCP.
List and search files: list folder children, search by name below a workspace folder, and list credential-free share metadata.
Read file metadata and content: get file info, read UTF-8 text files, and download small binary files as base64.
Write and manage files: write text files, upload base64 files, create folders, move/rename files, and delete files (root deletion refused; overwrite is opt-in).
Manage connections: begin/poll Nextcloud Login Flow v2 connections, set the Nextcloud root, and disconnect.
Manage household accounts and invoices: configure household accounts, prepare a household workspace, list accounts/invoices, review invoices conservatively, and save invoice reviews.
Allows ChatGPT and Codex to work with files in a user-owned Nextcloud workspace, providing tools for file management, capabilities discovery, app and share inventory, and household invoice review.
Integrates with OpenAI's ChatGPT and Codex to enable AI agents to access and manage Nextcloud files and perform household invoice reviews through the bridge.
Uses PostgreSQL for encrypted storage of connection metadata and credentials, supporting tenant-scoped data persistence.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Nextcloud ChatGPT Bridge list files in my Nextcloud documents folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Nextcloud for ChatGPT & Codex

An open-source, tenant-isolated bridge that lets ChatGPT and Codex work with files in a user-owned Nextcloud workspace. The bridge keeps its OAuth identity separate from Nextcloud credentials and uses standards-based providers when native Nextcloud MCP capabilities are absent.
Product website: nextcloud-for-chatgpt.v4t0r.chatgpt.site

Release status
v0.3.2 is the current maintenance release. The production MCP endpoint and reviewer OAuth were
verified on 2026-10-17. OpenAI directory publication is blocked by an unavailable existing MCP
configuration in the submission portal; the app is not published. See the
current checkpoint. A source release is not store approval.
The repository contains the application-side pieces required for a universal OAuth-protected MCP service:
request-scoped bridge identity and pseudonymous tenant isolation
Nextcloud Login Flow v2 without collecting a user's Nextcloud password
tenant-scoped metadata plus encrypted PostgreSQL credential storage
root-bound WebDAV and OCS providers with explicit read/write tools
conservative household invoice review that never approves, books, pays, or transmits
rate limiting, request limits, security headers, trusted-host checks, and stateless MCP transport
a DNS-rebinding-resistant HTTPS egress proxy and network-isolated production composition
database migrations, readiness checks, maintenance cleanup, and release preflight
a Codex plugin package plus reviewer-ready OpenAI listing and test material
a production landing site with privacy, terms, support, and security pages
The production service is deployed, but this source release does not claim OpenAI approval. Self-hosted installations require their own production domain, OAuth configuration and credentials.
The MCP bridge itself works without directory publication. Codex CLI, ChatGPT desktop, and the Codex IDE extension can connect directly; compatible remote MCP hosts can use a deployed HTTPS endpoint. ChatGPT web requires developer-mode access for an unpublished connection or installation of a published plugin. See deployment modes.
Related MCP server: C2C Bridge
Real Nextcloud validation
The standards-based fallback path passed a live integration run against Nextcloud 33.0.7:
authenticated OCS discovery
WebDAV listing, create, upload, download, metadata lookup, move, and cleanup
user-visible app inventory and root-bound share inventory
isolated synthetic household workspace and invoice-review flow
Native Nextcloud Context Agent MCP was unavailable on that instance. The successful fallback run is therefore direct evidence that native MCP is optional rather than a hidden dependency. No credentials or instance-identifying values are recorded. See the compatibility matrix.
Architecture
ChatGPT / Codex
|
| OAuth access token
v
Public stateless MCP boundary
|
| verified issuer + subject + scopes
v
BridgeSessionContext
|
| pseudonymous tenant scope
v
ConnectionService
|-- PostgreSQL connection metadata
`-- AES-256-GCM credential store
|
| Nextcloud Login Flow v2 credential
v
Root-bound provider core
|-- WebDAV files
|-- OCS capabilities, apps, shares, revocation
`-- Native Nextcloud MCP discovery when availableThe bridge identity never contains a Nextcloud username or credential. Every connection, pending flow, household profile, and credential operation is scoped by the verified tenant context.
Public MCP tools
Read and discovery
get_nextcloud_capabilitiesget_nextcloud_app_accessesprobe_native_nextcloud_mcplist_files,search_files,list_nextcloud_sharesget_file_info,read_text_file,download_file_base64list_nextcloud_connections,list_household_accounts,list_household_invoicesreview_household_invoice
Create or modify private Nextcloud state
write_text_file,upload_file_base64,create_folder,move_file,delete_filebegin_nextcloud_connection,poll_nextcloud_connection,set_nextcloud_rootdisconnect_nextcloudconfigure_household_account,prepare_household_workspacesave_household_invoice_review
Every hosted tool has an explicit title, description, input schema, output schema, and risk
annotations. The production tool contract is locked by automated tests and documented in
submission/TOOL_ANNOTATIONS.md.
Security defaults
account root
/and parent traversal are rejected before provider accessevery returned WebDAV path is rechecked against the configured root
HTTPS and TLS verification are mandatory for hosted Nextcloud targets
public targets are resolved, validated, and IP-pinned by a CONNECT-only egress proxy
bearer tokens, app passwords, share tokens, raw invoice text, and full IBANs are excluded from model-visible results
credential ciphertext is tenant-bound through AES-GCM authenticated data
overwrite is opt-in; the configured root cannot be deleted
request body and transfer sizes are bounded
write, overwrite, move, delete, disconnect, and credential-revocation risks are explicit
hosted access is stateless and derives a fresh identity for every MCP request
Read SECURITY.md before deployment. Report vulnerabilities through
GitHub private vulnerability reporting,
never through a public issue containing secrets or private data.
Local development
Requires Python 3.11 or newer.
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e ".[dev,hosted]"
ruff check .
pytestCopy .env.example to .env only for local testing. Use a dedicated Nextcloud account and app
password, keep the root narrow, and never commit the resulting file.
Run the local stdio server:
nextcloud-chatgpt-bridgeRun sanitized read-only diagnostics or the explicit temporary write/cleanup smoke test:
nextcloud-chatgpt-diagnose
nextcloud-chatgpt-diagnose --write-testProduction deployment
The reference composition is in deploy/compose.production.yml.
It separates PostgreSQL, the bridge, maintenance, egress, and TLS termination, and keeps the bridge
off the direct external network.
cp deploy/.env.production.example deploy/.env.production
docker compose --env-file deploy/.env.production \
-f deploy/compose.production.yml config
docker compose --env-file deploy/.env.production \
-f deploy/compose.production.yml up -dSupply database and encryption secrets as files outside Git. Apply migrations through the dedicated
migrate service, then run nextcloud-chatgpt-preflight against the exact public MCP, OAuth,
website, support, privacy, and terms URLs before any reviewer access.
See docs/PRODUCTION_DEPLOYMENT.md and
docs/HOSTED_ACCEPTANCE.md.
OpenAI submission package
Repository-side review material lives in submission/:
canonical listing copy and starter prompts
positive and negative reviewer cases
reviewer fixture and runbook
exact tool-annotation inventory
release notes and final operational checklist
The final OpenAI submission remains an owner-controlled action. See
docs/PLUGIN_SUBMISSION.md.
Project documents
License
Licensed under the Apache License 2.0. This independent project is not affiliated with or endorsed by Nextcloud GmbH or OpenAI.
Available Tools
14 toolscreate_folderCreate Nextcloud folderA
Create one folder only inside the user's connected private Nextcloud workspace root.
Uses the stored account connection; does not create public shares or contact another host.
Inputs: path (required). Returns: etag, name, path, size, +3 more
delete_fileDelete Nextcloud fileADestructiveIdempotent
Delete one item only inside the user's connected private Nextcloud workspace root.
Deleting the root itself is refused. Cannot target another account, host, or arbitrary URL.
Inputs: path (required). Returns: ok, path, message
download_file_base64Download Nextcloud file as base64ARead-only
Read one small binary file from the user's private Nextcloud workspace as base64.
Enforces the transfer size limit; the destination is the stored account, not an arbitrary URL.
Inputs: path (required). Returns: path, size, content_type, content_base64
get_file_infoGet Nextcloud file infoARead-only
Read one item's metadata inside the user's connected private Nextcloud workspace root.
The relative path cannot select another account, host, or public internet resource.
Inputs: path (required). Returns: etag, name, path, size, +3 more
get_nextcloud_app_accessesInspect accessible Nextcloud appsARead-only
Read apps visible to the user's connected private Nextcloud account.
Uses only that account's stored server and permissions; no administrator APIs or other hosts.
Inputs: no named parameters. Returns: apps, warnings, search_providers, nextcloud_version
get_nextcloud_capabilitiesInspect Nextcloud capabilitiesARead-only
Read capability hints only from the user's authenticated, connected Nextcloud server.
The destination is the stored account connection, not an arbitrary URL or public web search.
Inputs: no named parameters. Returns: app_api_hint, version_major, version_micro, version_minor, +5 more
list_filesList Nextcloud filesARead-only
List direct children inside the user's connected private Nextcloud workspace root.
Paths are relative to that root; this cannot browse another account, host, or the public web.
Inputs: path. Returns: path, entries
move_fileMove or rename Nextcloud fileBDestructive
Move or rename an item within the user's connected private Nextcloud workspace root.
Both paths stay inside the same account and root; no transfer to another host or recipient.
Inputs: source (required), destination (required), overwrite. Returns: etag, name, path, size, +3 more
probe_native_nextcloud_mcpProbe native Nextcloud MCPARead-only
Check MCP availability only on the user's stored Nextcloud account connection.
Performs discovery without invoking a native tool or contacting an unrelated destination.
Inputs: no named parameters. Returns: endpoint, available, tool_names, tools_truncated, +1 more
read_text_fileRead Nextcloud text fileARead-only
Read bounded UTF-8 content from the user's connected private Nextcloud workspace root.
Enforces the transfer size limit and cannot fetch arbitrary URLs or files outside that root.
Inputs: path (required). Returns: path, size, content, encoding
search_filesSearch files inside the Nextcloud workspaceBRead-only
Search filenames only inside the user's connected private Nextcloud workspace root.
This is a bounded account search, not public web search or a search of other destinations.
Inputs: query (required), path, max_depth, max_results. Returns: path, query, entries, truncated, +1 more
upload_file_base64Upload Nextcloud file from base64ADestructive
Write a small binary file only inside the user's private Nextcloud workspace root.
Enforces strict base64 and size limits. Existing files require overwrite=true; no public sharing.
Inputs: path (required), content_base64 (required), overwrite. Returns: etag, name, path, size, +3 more
write_text_fileWrite Nextcloud text fileADestructive
Write UTF-8 content only inside the user's connected private Nextcloud workspace root.
Existing files require overwrite=true. Does not publish content, create shares, or send messages.
Inputs: path (required), content (required), overwrite. Returns: etag, name, path, size, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
File operations are clearly separated by action and by text-vs-binary (read_text_file vs download_file_base64, write_text_file vs upload_file_base64). The three discovery tools (get_nextcloud_capabilities, get_nextcloud_app_accesses, probe_native_nextcloud_mcp) have distinct targets but their boundaries are subtler for an agent. No dangerous overlap among the core file tools.
All 14 tools use consistent snake_case with meaningful action verbs (list_, get_, read_, write_, upload_, download_, create_, move_, delete_, search_, probe_). The only minor inconsistency is the redundant 'nextcloud' prefix in some metadata tool names (get_nextcloud_capabilities, get_nextcloud_app_accesses, probe_native_nextcloud_mcp) while others omit the domain.
14 tools is well within the ideal range and each tool maps to a distinct file-management or metadata operation. The surface is neither bloated nor thin for a private workspace bridge.
Core lifecycle is covered: list/search/info, read text/binary, write/upload, create_folder, move/rename, delete. The notable gap is share management — list_nextcloud_shares exists but there is no create/delete share, so sharing workflows dead-end after reading. Minor and workable via other apps.
Maintenance
Related MCP Connectors
Connect AI agents to Filepad workspaces through OAuth MCP.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables to manage Nextcloud files, user info, sharing, calendar, and contacts through optimized MCP tools with dynamic tool selection and enterprise-grade security.891MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents like Codex to use the ChatGPT web app as a planning and review brain, letting ChatGPT read only needed code via OAuth MCP and submit locally authorized tasks without API keys or repository uploads.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT web to read local files, search code, run shell commands, and drive a local Codex CLI via an official MCP connector, with human approval for risky commands and full audit logging.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to securely control remote development servers over OAuth-protected MCP, exposing workspace-bounded tools for file editing, command execution, Git operations, and running Codex or GitHub Copilot subagents.27 npmMIT