List, search, download and upload files in a NAVER MYBOX (네이버 마이박스) cloud drive.
An MCP server for NAVER MYBOX (네이버 마이박스) — list, search, download and upload files in your MYBOX cloud drive from any MCP client (Claude Code, Claude Desktop, and others).
MYBOX opened a public API in August 2026 (developers.mybox.naver.com). This wraps it as tools. Unofficial, not affiliated with NAVER.
Phone photos land in MYBOX automatically. Getting them onto a machine meant clicking through the web UI. With this, an agent can fetch "every photo taken on 10–11 September" into a working folder in one step.
Requires Python 3.10+.
pip install naver-mybox-mcp
Authentication is a personal access token, not OAuth.
Up to five tokens per account; each lasts 30, 60, 90 or 180 days, and MYBOX emails you 7 days and 1 day before expiry. Anyone holding the token can reach the whole drive, so treat it as a password and never commit it.
Provide it as the MYBOX_PAT environment variable, or put it on one line in ~/.mybox/token.
{
"mcpServers": {
"mybox": {
"command": "naver-mybox-mcp",
"env": { "MYBOX_PAT": "mbx_pat_..." }
}
}
}
In Claude Code: claude mcp add mybox --env MYBOX_PAT=mbx_pat_... -- naver-mybox-mcp
| Tool | What it does |
|---|---|
mybox_storage | Quota, used bytes, per-category file counts, max upload size |
mybox_list | Entries directly inside a folder, or the drive root |
mybox_search | Search by keyword, category and/or date range (KST) |
mybox_file_info | Attributes of one file or folder |
mybox_download | Download one file into a local directory |
mybox_upload | Upload one local file |
mybox_create_folder | Create a folder |
The API can delete files, empty the trash and set its auto-delete period. Those tools are not exposed here. An agent that can read and write files is useful; one that can destroy them is a different risk, and the web UI is right there. Open an issue if you need them behind a flag.
The docs publish per-plan limits and warn that bursts or abuse may be blocked without prior notice, so the client paces itself below the lowest documented per-minute limits (9/min for search, 55/min otherwise). Free accounts can use the API; the plan only changes the limits.
| Plan | Downloads | Search | Other APIs |
|---|---|---|---|
| 30GB | 500/day | 10/min | 60/min each |
| 80GB | 1,000/day | 10/min | 60/min each |
| 180GB–330GB | 1,000/day | 30/min | 240/min each |
| 2TB | 2,000/day | 30/min | 240/min each |
Download limits are daily and the client cannot pace around them. Search first, count the results, and fetch in batches if the set is large.
https://open-api.mybox.naver.com/v1POST /drive/files returns an uploadUrl (48h, single use); the bytes
go there as multipart field Filedata.GET /drive/files/{id}/download returns a downloadUrl
(10 minutes, single use).responseMetaData.nextCursor goes back as cursor.The MYBOX API opened on 2026-08-10 and tooling appeared quickly. NAVER publishes no MCP server or SDK of its own, and its launch post does not mention MCP. Community work that exists:
| Project | What it is |
|---|---|
| minking/mybox-mcp | MCP server in TypeScript covering all 20 endpoints, including delete and trash |
| oliverne/myboxctl | CLI for file operations (@oliverne/myboxctl on npm) |
| overworks/php-mybox | PHP SDK, plus a Go CLI and a Flysystem adapter by the same author |
| chiwanpark/mybox-s3 | S3-compatible API in front of MYBOX |
This one is Python, exposes a deliberately smaller surface (no delete), paces itself under the documented rate limits, and ships tests that need neither a token nor the network. Pick whichever fits; if you want every endpoint including destructive ones, the TypeScript server above has them.
pip install -e ".[dev]"
pytest
Tests run against httpx.MockTransport; no token or network needed.
Releases are published from GitHub Actions on a GitHub release: PyPI via Trusted Publishing (no stored token) and the MCP registry via GitHub OIDC.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx naver-mybox-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-java-jaydev-naver-mybox-mcp": {
"command": "uvx",
"args": [
"naver-mybox-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencenaver-mybox-mcppypiNAVER MYBOX works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.