mybox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYBOX_ACCESS_TOKEN | Yes | Your MYBOX personal access 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dms_storageC | 내 파일 속성 조회 |
| dms_rootC | 루트 파일/폴더 목록 조회 |
| dms_listC | 특정 폴더 내 파일/폴더 목록 조회 |
| dms_resourceIdB | 개별 파일/폴더 속성 조회 |
| files_create_folderD | 폴더 생성 |
| files_uploadC | 파일 업로드 URL 생성 |
| files_downloadC | 파일 다운로드 URL 생성 |
| files_copyC | 파일/폴더 복사 |
| files_deleteC | 파일/폴더 삭제 |
| files_moveC | 파일/폴더 이동 |
| files_renameC | 파일/폴더 이름 변경 |
| dms_favoriteC | 즐겨찾기 표시 |
| dms_unfavoriteC | 즐겨찾기 해제 |
| search_files_resourcesD | 파일 검색 |
| search_folders_resourcesD | 폴더 검색 |
| dms_trash_listC | 휴지통 목록 조회 |
| files_trash_restoreD | 휴지통 복원 |
| files_trash_clean_resourceIdB | 휴지통 특정 파일 삭제 (영구삭제) |
| files_trash_cleanB | 휴지통 전체 삭제 |
| dms_trash_routineC | 휴지통 자동 삭제 주기 설정 |
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 20 tools
Most tools target a distinct resource+action (list, copy, move, rename, delete, trash, favorite, search). Minor overlap exists between dms_storage and dms_resourceId (both 'property inquiry') and between dms_root and dms_list, but descriptions clarify most boundaries.
Three prefix families coexist (dms_, files_, search_) with mixed structure: some dms_ tools are nouns (dms_storage, dms_root), others are verbs (dms_favorite, dms_unfavorite), plus camelCase suffixes (dms_resourceId, files_trash_clean_resourceId) mixed with snake_case. Still readable but not one predictable pattern.
At 20 tools the surface is on the heavy side for a file manager, but each tool maps to a genuine operation (CRUD, trash lifecycle, search, favorites, storage). A few could be consolidated (search_files/search_folders, dms_root/dms_list) but nothing feels redundant filler.
Strong lifecycle coverage: list/properties, create folder, upload/download, copy/move/rename/delete, full trash management (list/restore/clean/clean-one/routine), search, and favorites. Gaps are secondary features like sharing/permissions, file creation, or versioning rather than core workflows.