mcp-pcloud-crunchtools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PCLOUD_API_HOST | No | api.pcloud.com (default) or eapi.pcloud.com for EU accounts | api.pcloud.com |
| PCLOUD_ACCESS_TOKEN | No | pCloud OAuth access token. Exactly one of PCLOUD_ACCESS_TOKEN or PCLOUD_ACCESS_TOKEN_FILE is required. | |
| PCLOUD_ACCESS_TOKEN_FILE | No | Path to a file holding the token — preferred, takes precedence. Exactly one of PCLOUD_ACCESS_TOKEN or PCLOUD_ACCESS_TOKEN_FILE is required. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pcloud_list_folderC | List contents of a folder in pCloud with file and folder metadata. |
| pcloud_create_folderC | Create a folder in pCloud, succeeding if it already exists. |
| pcloud_delete_folderA | Delete a folder in pCloud. Set recursive to remove its contents too. |
| pcloud_rename_folderC | Rename or move a folder in pCloud. |
| pcloud_copy_folderB | Copy a folder in pCloud to a new location. |
| pcloud_get_file_infoC | Get metadata for a file in pCloud. |
| pcloud_delete_fileC | Delete a file from pCloud. |
| pcloud_rename_fileC | Rename or move a file in pCloud. |
| pcloud_copy_fileC | Copy a file in pCloud to a new location. |
| pcloud_read_text_fileA | Read the contents of a UTF-8 text file stored in pCloud. |
| pcloud_get_checksumA | Get pCloud's stored SHA256, SHA1, and MD5 checksums for a file. |
| pcloud_get_file_linkA | Get a temporary direct download URL for a file in pCloud. |
| pcloud_create_public_linkA | Create a public share link for a file, exposing it to anyone with the URL. |
| pcloud_searchA | Search pCloud for files and folders whose names match a query. |
| pcloud_get_user_infoA | Get the authenticated pCloud account's profile and quota usage. |
| pcloud_auth_statusA | Report whether this server currently holds a usable pCloud credential. Call this first. It says whether the server can reach pCloud, and if it cannot, what is missing and which tool fixes it. |
| pcloud_auth_startA | Begin browser authorization and return the URL for the user to approve. Open the returned URL. The user approves there, pCloud redirects back to this server, and the token is stored automatically -- nothing is copied back by hand. Then call pcloud_auth_status to confirm. |
| pcloud_auth_resultA | Report the outcome of the most recent authorization redirect. |
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 18 tools
Each tool targets a distinct resource and action, with clear separation between folder and file operations. The file metadata/link tools (get_file_info, get_checksum, get_file_link, create_public_link) are differentiated by their specific outputs. Auth tools follow a clear three-step lifecycle with no overlap.
All tool names follow a consistent pcloud_ prefix with a verb_noun pattern (list_folder, delete_file, get_checksum). Auth tools share the pcloud_auth_ sub-pattern, and naming style is uniform. This makes tool selection highly predictable.
At 18 tools, the count slightly exceeds the ideal 3-15 range but remains reasonable for a comprehensive cloud storage server. Each tool covers a meaningful operation with no redundancy, so the set is still well-scoped.
The server provides solid folder and file metadata management, but notably lacks any upload or file creation capability, leaving no way to create or modify file content. Binary file download is also absent, with only text reading and URL generation available. These are significant gaps for a storage server's core purpose.