A side-by-side look at the Clicksend MCP Server and Pipedream MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clicksend MCP Server for developer tools work as a local process; choose Pipedream for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
CLICKSEND_USERNAME, CLICKSEND_API_KEY.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | CLICKSEND_USERNAMECLICKSEND_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 11,720 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Clicksend MCP Server | View Pipedream |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"clicksend-mcp-server": {
"command": "npx",
"args": [
"-y",
"@clicksend/clicksend-mcp-server@latest"
],
"env": {
"CLICKSEND_USERNAME": "YOUR_CLICKSEND_USERNAME_HERE",
"CLICKSEND_API_KEY": "YOUR_CLICKSEND_API_KEY_HERE"
}
}
}
}
{
"mcpServers": {
"pipedreamhq-pipedream": {
"url": "https://pipedream.com/docs/api/sse/"
}
}
}