Drop to CDN vs Putput MCP
A side-by-side look at the Drop to CDN and Putput MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Drop to CDN for file systems work as a local process; choose Putput MCP 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 Drop to CDN when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DROPTOCDN_API_KEY, DROPTOCDN_API_URL. - You want tools like
upload_file, get_file, list_files.
Choose Putput MCP when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
upload_file, list_files, delete_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 51/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DROPTOCDN_API_KEYDROPTOCDN_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Drop to CDN | View Putput MCP |
Tools & capabilities
Drop to CDN tools 4
upload_fileUpload a local file or base64 content → public CDN URLget_fileGet CDN URL and metadata by file IDlist_filesList files in your account (paginated)delete_filePermanently delete a file by ID
Putput MCP tools 4
upload_fileUpload a file from a URL to PutPut and get a CDN link backlist_filesList uploaded files with optional prefix filter and paginationdelete_fileDelete a file by IDget_file_infoGet file details, stats, and download URL
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.
Drop to CDN
{
"mcpServers": {
"drop-to-cdn": {
"command": "npx",
"args": [
"-y",
"mcp-server-droptocdn"
],
"env": {
"DROPTOCDN_API_KEY": "YOUR_DROPTOCDN_API_KEY_HERE",
"DROPTOCDN_API_URL": "YOUR_DROPTOCDN_API_URL_HERE"
}
}
}
}
Putput MCP
{
"mcpServers": {
"putput-mcp": {
"command": "npx",
"args": [
"@putput/mcp"
]
}
}
}
Frequently asked questions
Drop to CDN is categorized under File Systems and uses a local stdio subprocess. Putput MCP belongs to File Systems and uses a local stdio subprocess. Pick Drop to CDN for file systems work and Putput MCP 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.
Drop to CDN has no declared pricing — check the project's own site. Putput MCP 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 drop-to-cdn and putput-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Drop to CDN has a quality signal of 51/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Putput MCP has 49/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.
