AdCrunch vs Linkedin Humblebrag
A side-by-side look at the AdCrunch and Linkedin Humblebrag MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AdCrunch for social media work over a hosted endpoint; choose Linkedin Humblebrag for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AdCrunch when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_advertisers, list_campaigns, list_ad_groups.
Choose Linkedin Humblebrag when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
linkedin_humblebrag_generate.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 52/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
AdCrunch tools 8
list_advertisersConnected ad accounts across platformslist_campaignsCampaigns for an advertiserlist_ad_groupsAd-group structurelist_adsIndividual adsquery_insightsTime-series performance: spend, ROAS, CPA, impressions, clicks, conversionssearch_adsSearch ad creativeskill_listDiscover and fetch your org's reusable ad-ops playbooksskill_createAuthor and maintain playbooks (Skills store)
Linkedin Humblebrag tools 1
linkedin_humblebrag_generateGenerate a humorous LinkedIn post from an achievement. Input your accomplishment and get back a self-deprecating post with vulnerability and humor. Returns the post text ready to share.
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.
AdCrunch
{
"mcpServers": {
"adcrunch": {
"url": "https://mcp.adcrunch.dev/mcp"
}
}
}
Linkedin Humblebrag
{
"mcpServers": {
"linkedin-humblebrag": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-linkedin-humblebrag"
]
}
}
}
Frequently asked questions
AdCrunch is categorized under Social Media and uses a remote HTTP/SSE transport. Linkedin Humblebrag belongs to Social Media and uses a local stdio subprocess. Pick AdCrunch for social media work and Linkedin Humblebrag for social media.
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.
AdCrunch has no declared pricing — check the project's own site. Linkedin Humblebrag 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 adcrunch and linkedin-humblebrag as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AdCrunch has a quality signal of 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Linkedin Humblebrag has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.