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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_nextcloud_capabilitiesA | 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. |
| get_nextcloud_app_accessesA | 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. |
| probe_native_nextcloud_mcpA | Check MCP availability only on the user's stored Nextcloud account connection. Performs discovery without invoking a native tool or contacting an unrelated destination. |
| list_filesA | 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. |
| search_filesB | 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. |
| list_nextcloud_sharesB | Read existing share metadata only for items inside the user's private workspace root. Uses the connected account's permissions; never creates shares or publishes file content. |
| get_file_infoA | 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. |
| read_text_fileA | 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. |
| download_file_base64A | 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. |
| write_text_fileA | 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. |
| upload_file_base64A | 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. |
| create_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. |
| move_fileB | 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. |
| delete_fileA | 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. |
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
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.