CloudPaste MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDPASTE_URL | Yes | CloudPaste root URL, only http(s) allowed. | |
| CLOUDPASTE_API_KEY | Yes | Dedicated CloudPaste API Key with minimum permission value 10. | |
| CLOUDPASTE_DEFAULT_PATH | No | Default upload directory. | |
| CLOUDPASTE_STORAGE_CONFIG_ID | No | Default target storage configuration ID. Defaults to CloudPaste default storage. | |
| CLOUDPASTE_DEFAULT_EXPIRES_HOURS | No | Default share expiration in hours, range 1-8760. | 24 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test_connectionA | 验证 CloudPaste URL 与 API Key 是否有效，并返回当前密钥的非敏感权限摘要。不会返回或记录 API Key。 |
| upload_fileA | 上传调用方明确指定的本地普通文件，并创建远程分享。默认有效期为 24 小时且强制使用 CloudPaste 受控代理下载链接；成功后返回下载直链、文件 ID 与过期时间。 |
| list_filesB | 分页查询当前 CloudPaste API Key 自己创建的远程文件。支持按关键词搜索；不会返回密码、密钥或其他敏感字段。 |
| get_fileA | 查询当前 API Key 自己创建的一个 CloudPaste 文件的详情；默认返回最新受控预览与下载链接，并且过滤任何密码或密钥字段。 |
| delete_filesA | 不可恢复地删除当前 API Key 自己创建的 CloudPaste 文件：同时删除分享记录和底层 WebDAV/S3 对象。仅在已经获得用户明确删除授权后调用，且必须传 confirm=true。 |
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 5 tools
Each tool targets a distinct action and resource: delete_files deletes, upload_file uploads, list_files lists, get_file retrieves details, and test_connection validates credentials. There is no overlap in purpose.
All tool names follow a consistent snake_case verb_noun pattern (delete_files, test_connection, upload_file, list_files, get_file). The convention is predictable throughout.
Five tools cover the essential file management surface (upload, list, get, delete, and connection test) without redundancy. This is well-scoped for the server's purpose.
The tool set covers create, read, and delete operations, but lacks any update operation (e.g., renaming a file, changing expiration, or updating metadata). This is a notable gap for a file management server, though core workflows are present.