mybox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYBOX_PAT | Yes | Personal access token for the NAVER MYBOX Open API. Can alternatively be provided on one line in ~/.mybox/token. |
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 |
|---|---|
| mybox_storageA | Report MYBOX quota, used bytes, per-category file counts and max upload size. |
| mybox_listA | List files and folders directly inside a folder, or the drive root. Args: folder_id: Folder to list. Omit for the drive root. count: Maximum entries to return (the API pages internally, 1000 per page). sort: "field,direction" where field is name, createdAt, modifiedAt or accessedAt. |
| mybox_searchA | Search files by keyword, category and/or date range. At least one is required. Args: query: Keyword. Spaces and extensions are combined with AND. category: One of image, video, audio, document, archive, executable, etc. start_date: Inclusive start, YYYY-MM-DD, interpreted in KST. end_date: Inclusive end, YYYY-MM-DD, interpreted in KST. date_field: Which date the range applies to: "created" or "modified". parent_path: Restrict the search to this folder path and below. max_items: Stop after this many results. |
| mybox_file_infoC | Fetch the attributes of one file or folder by id. |
| mybox_downloadA | Download one file into a local directory and return the path written. A local file with the same name and size is left in place and reported as skipped. Download quotas are per day and small on entry plans, so avoid re-downloading. |
| mybox_uploadA | Upload one local file to MYBOX. Args: path: Local file to upload. parent_id: Destination folder id. Omit to upload to the drive root. overwrite: Replace an existing file with the same name instead of keeping both. |
| mybox_create_folderA | Create a folder and return its id. Args: name: Folder name. parent_id: Parent folder id. Omit to create it at the drive root. |
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 operation: aggregate quota, folder listing, single-item info, search, download, upload, and folder creation. Overlap is minimal; the list/search distinction is clear (browse vs query).
All names use the mybox_ prefix and snake_case, making them predictable and readable. There is a minor mix of verb-based (list, search, download, upload) and noun-based (storage, file_info) names, but no confusing inconsistency.
Seven tools cover the essential storage operations without redundancy. Each tool earns its place and the set is well-scoped for a cloud storage MCP.
Core read, write, and create operations are present, but the lifecycle is incomplete: there is no delete, move/rename, or copy operation. These are notable gaps for a file management server.