Nextcloud ChatGPT Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nextcloud_capabilitiesA | Inspect server/app capability hints used to choose native Nextcloud or fallback providers. |
| get_nextcloud_app_accessesA | Inventory user-visible apps and safe bridge access levels without administrator APIs. |
| probe_native_nextcloud_mcpA | Check whether Nextcloud Context Agent MCP is reachable; never invokes a native tool. |
| list_filesA | List direct children of a folder inside the configured Nextcloud root. |
| search_filesA | Search names below one workspace folder without crossing the configured root. |
| list_nextcloud_sharesA | List credential-free share metadata constrained to the configured workspace root. |
| get_file_infoA | Get metadata for one file or folder inside the configured Nextcloud root. |
| read_text_fileA | Read a UTF-8 text file, subject to the configured MCP transfer size limit. |
| download_file_base64A | Download a small binary file as base64, subject to the MCP transfer size limit. |
| write_text_fileA | Write a UTF-8 text file. Existing files are protected unless overwrite is explicitly true. |
| upload_file_base64B | Upload a small binary file from strict base64 data, subject to the transfer size limit. |
| create_folderA | Create a folder inside the configured Nextcloud root. |
| move_fileA | Move or rename a file/folder inside the configured root. |
| delete_fileA | Delete one file or folder. Deleting the configured root itself is always refused. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.