Filesystem vs NAVER MYBOX
A side-by-side look at the Filesystem and NAVER MYBOX MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose NAVER MYBOX for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Choose NAVER MYBOX when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MYBOX_PAT. - You want tools like
mybox_storage, mybox_list, mybox_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 90/100 · Excellent | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | MYBOX_PAT |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,405 | 1 |
| Directory activity | 8 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | 7 |
| Full listing | View Filesystem | View NAVER MYBOX |
Tools & capabilities
Filesystem tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
NAVER MYBOX tools 7
mybox_storageReport MYBOX quota, used bytes, per-category file counts and max upload size.mybox_listList 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_searchSearch 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_infoFetch the attributes of one file or folder by id.mybox_downloadDownload 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_uploadUpload 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_folderCreate a folder and return its id. Args: name: Folder name. parent_id: Parent folder id. Omit to create it at the drive root.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
NAVER MYBOX
{
"mcpServers": {
"naver-mybox": {
"command": "uvx",
"args": [
"naver-mybox-mcp"
],
"env": {
"MYBOX_PAT": "YOUR_MYBOX_PAT_HERE"
}
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. NAVER MYBOX belongs to File Systems and uses a local stdio subprocess. Pick Filesystem for file systems work and NAVER MYBOX for file systems.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Filesystem is listed as free. Auth: no auth required. NAVER MYBOX has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add filesystem and naver-mybox as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Filesystem has a quality signal of 90/100 (Excellent) with 8 views, 0 installs and 91,405 GitHub stars. NAVER MYBOX has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.