Ctxd vs Drop to CDN
A side-by-side look at the Ctxd and Drop to CDN MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ctxd for file systems work as a local process; choose Drop to CDN 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 Ctxd 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 47/100 · Fair | 51/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 | DROPTOCDN_API_KEYDROPTOCDN_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 63 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Ctxd | View Drop to CDN |
Tools & capabilities
Ctxd tools
No tool names declared yet. Check the project README from the listing page.
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
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.
Ctxd
{
"mcpServers": {
"ctxd": {
"command": "uvx",
"args": [
"ctxd"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Ctxd is categorized under File Systems and uses a local stdio subprocess. Drop to CDN belongs to File Systems and uses a local stdio subprocess. Pick Ctxd for file systems work and Drop to CDN 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.
Ctxd is listed as free. Auth: no auth required. Drop to CDN 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 ctxd and drop-to-cdn as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ctxd has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 63 GitHub stars. Drop to CDN has 51/100 (Good) with 2 views, 0 installs and 0 GitHub stars.