Filesystem vs MCP Upload
A side-by-side look at the Filesystem and MCP Upload 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 MCP Upload 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 MCP Upload when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OBJEKT_API_KEY. - You want tools like
upload_file, upload_from_sandbox, get_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 90/100 · Excellent | 45/100 · Fair |
| 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 | OBJEKT_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,405 | 0 |
| Directory activity | 8 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 9 | 4 |
| Full listing | View Filesystem | View MCP Upload |
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
MCP Upload tools 4
upload_fileUpload by host path or inline contentupload_from_sandboxReturns curl command for sandbox uploadsget_fileGet file metadata and permalinkget_pricingCurrent storage tier pricing
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"
]
}
}
}
MCP Upload
{
"mcpServers": {
"mcp-upload": {
"command": "npx",
"args": [
"-y",
"@objekt.sh/mcp-upload"
],
"env": {
"OBJEKT_API_KEY": "YOUR_OBJEKT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. MCP Upload belongs to File Systems and uses a local stdio subprocess. Pick Filesystem for file systems work and MCP Upload 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. MCP Upload 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 mcp-upload 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. MCP Upload has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
