Vibeads MCP vs Tin
A side-by-side look at the Vibeads MCP and Tin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vibeads MCP for marketing work as a local process; choose Tin for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vibeads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VIBEADS_API_KEY. - You want tools like
list_campaigns, get_campaign_details, get_account_health_score.
Choose Tin when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 57/100 · Good | 45/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 | VIBEADS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 263 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 29 | Not listed |
| Full listing | View Vibeads MCP | View Tin |
Tools & capabilities
Vibeads MCP tools 29
list_campaignsYour campaigns in VibeAds (published, imported and drafts) with status, budget and category. Campaigns only in your Google Ads account are listed by `find_campaigns_to_importget_campaign_detailsDeep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnosticsget_account_health_score0-100 score + letter grade across 6 dimensions, optionally per-campaignget_search_term_analysisWasted spend + winners from each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)get_diagnosticsLatest agent-optimize diagnostics with severity + recommended fix (up to 50)find_campaigns_to_importBefore importing: the campaigns in your Google Ads account, read from Google Ads, each marked with whether it is in VibeAds (VibeAds manages only the campaigns in it). Called `list_google_ads_campaigns` in 0.2.15get_performance_reportOne campaign's or a whole account's figures for a period you choose (a preset or two dates, up to 90 days), read live from Google Ads, optionally by day, device, hour, ad group, keyword or location. Money in the account's currency. VibeAds builds every query; the assistant only picks the period and…audit_google_ads_accountAn audit of one connected Google Ads account, read live from Google Ads: up to 25 Search campaigns over the last 30 days, whether or not they are in VibeAds, with a 0-100 health score and grade for the account and each campaign, the issues grouped by check with what fixes each in Google Ads, and ea…list_keywordsOne published campaign's ad groups, keywords and negative keywords, read live from Google Ads: match type, status, max CPC and 30 days of clicks, cost and conversionsresearch_keywordsKeyword ideas from Google's Keyword Planner for seed keywords, a web page or both, in the places you name: average monthly searches, competition and top-of-page bid range. Pro/Max, 2 credits (a repeat within 90 days is free)list_google_ads_accountsEvery connected Google Ads account, switched on or not, with the manager account (MCC) each client account sits underlist_google_recommendationsGoogle's own recommendations for an account (its Recommendations page), with Google's estimate and whether each can be applied from the chat- +17 more on the listing page
Tin tools
No tool names declared yet. Check the project README from the listing page.
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.
Vibeads MCP
{
"mcpServers": {
"mcp-335": {
"command": "npx",
"args": [
"-y",
"@vibeads/mcp"
],
"env": {
"VIBEADS_API_KEY": "YOUR_VIBEADS_API_KEY_HERE"
}
}
}
}
Tin
{
"mcpServers": {
"tin": {
"url": "https://app.tin.computer/mcp"
}
}
}
Frequently asked questions
Vibeads MCP is categorized under Marketing and uses a local stdio subprocess. Tin belongs to Marketing and uses a remote HTTP/SSE transport. Pick Vibeads MCP for marketing work and Tin for marketing.
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.
Vibeads MCP has no declared pricing — check the project's own site. Tin 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 mcp-335 and tin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vibeads MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Tin has 45/100 (Fair) with 1 views, 0 installs and 263 GitHub stars.