couchdrop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COUCHDROP_API_BASE | No | Base URL for Couchdrop management API requests. | https://api.couchdrop.io |
| COUCHDROP_API_TOKEN | Yes | Couchdrop API token sent to Couchdrop API and FileIO requests. | |
| COUCHDROP_FILEIO_BASE | No | Base URL for Couchdrop FileIO requests. | https://fileio.couchdrop.io |
| COUCHDROP_MAX_INLINE_BYTES | No | Maximum bytes returned inline for downloads without outputPath. | 65536 |
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 |
|---|---|
| couchdrop_list_filesD | – |
| couchdrop_get_file_infoD | – |
| couchdrop_download_fileD | – |
| couchdrop_upload_fileD | – |
| couchdrop_list_usersD | – |
| couchdrop_list_groupsD | – |
| couchdrop_get_folder_permissionsD | – |
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 7 tools
Each tool targets a distinct file or administrative operation (download, get info, list, upload, permissions, groups, users) with no overlap in purpose, making them easily distinguishable even without descriptions.
All tools follow the consistent 'couchdrop_verb_noun' pattern (e.g., couchdrop_download_file, couchdrop_list_users), with no mixing of conventions or ambiguous verbs.
Seven tools is well-scoped for a file management and permissions service; not too few to feel thin nor too many to overwhelm, covering core operations without redundancy.
Covers key file operations (upload, download, list, info) and some admin actions (list users/groups, get permissions), but notably lacks file deletion, file update, and any user/group creation or modification, creating significant gaps for full lifecycle management.