A side-by-side look at the Bangermap and Youtube Growth MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bangermap for social media work as a local process; choose Youtube Growth for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
YOUTUBE_API_KEY.Rows where the two servers differ are marked.
| Spec | Y Youtube Growth | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 41/100 · Fair | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | YOUTUBE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bangermap | View Youtube Growth |
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": {
"bangermap": {
"command": "npx",
"args": [
"-y",
"bangermap-mcp"
],
"env": {
"YOUTUBE_API_KEY": "YOUR_YOUTUBE_API_KEY_HERE"
}
}
}
}
{
"mcpServers": {
"youtube-growth-2": {
"url": "https://www.dapdip.com/mcp"
}
}
}