Nextcloud ChatGPT Bridge
Related Servers
Alternatives to Nextcloud ChatGPT Bridge
No user-submitted related servers found.
Related Servers
- 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.35 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables to manage Nextcloud files, user info, sharing, calendar, and contacts through optimized MCP tools with dynamic tool selection and enterprise-grade security.MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT Pro web to securely read workspace files, git diffs, and test records through OAuth-protected read-only MCP tools, so it can plan and review while Codex handles execution without uploading the repository.MIT

PC FileBridgeofficial
AlicenseNot gradedqualityAmaintenanceEnables ChatGPT, Codex, and compatible MCP clients to read bounded UTF-8 text and create files or directories in operator-selected folders, with strict protections against overwrites, deletes, and path escapes.Apache 2.0
TDQS
Scored across 14 tools
Tools address distinct resources/actions (capabilities, app access, file ops, shares), but get_nextcloud_capabilities, get_nextcloud_app_accesses, and probe_native_nextcloud_mcp all concern bridge/native capability discovery and could be confused if descriptions are skimmed. The file tools are clearly distinct: list/search/get/read/write/upload/create/move/delete.
Most names follow a verb_noun snake_case pattern (list_files, create_folder, delete_file), but there is minor inconsistency between get_ prefixed tools (get_nextcloud_capabilities), bare verbs (read_text_file, write_text_file), and descriptive verbs (probe_native_nextcloud_mcp, download_file_base64). Still predictable and readable overall.
14 tools is well within the ideal range for a file-management bridge with additional introspection. Each tool covers a concrete, non-redundant operation; none feel like padding.
File lifecycle is well covered: list, search, read, write, upload, download, create, move, delete, and metadata. Missing share management (only listing) and lack of a direct 'exists' endpoint (though get_file_info covers it), but these are minor gaps for the bridge's apparent scope.