A side-by-side look at the Appwrite MCP and Clicksend MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Appwrite MCP for developer tools work over a hosted endpoint; choose Clicksend MCP Server for developer tools as a local process. 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 | 76/100 · Great | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | CLICKSEND_USERNAMECLICKSEND_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 72 | 3 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Appwrite MCP | View Clicksend MCP Server |
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": {
"appwrite-mcp": {
"url": "https://mcp.appwrite.io/"
}
}
}
{
"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"
}
}
}
}