What is the key difference between Vibeads MCP and PushEngage?

Vibeads MCP belongs to the Marketing category with local stdio execution, while PushEngage belongs to the Marketing category with local stdio execution.

How do I install Vibeads MCP or PushEngage in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Vibeads MCP and PushEngage free or paid?

Vibeads MCP operates under a Free / Open Source model (No auth required). PushEngage operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Vibeads MCP lists 14 tools with 0 views and 1 GitHub stars. PushEngage lists 21 tools with 0 views and 8 GitHub stars.

Can I use both Vibeads MCP and PushEngage together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Vibeads MCP vs PushEngage

In-depth architectural comparison of the Vibeads MCP and PushEngage MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Vibeads MCP

Marketing · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

PushEngage

Marketing · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Verdict Summary: Choose Vibeads MCP if you need specialized Marketing tools running via a local process. Choose PushEngage if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Vibeads MCP when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: VIBEADS_API_KEY.
Primary tools included: list_campaigns, get_campaign_details, get_account_health_score.

Explore Vibeads MCP Details

Choose PushEngage when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: PE_MCP_CLIENT_NAME, PE_MCP_CONFIG_PATH.
Primary tools included: pushengage_auth_login, pushengage_auth_status, pushengage_auth_logout.

Feature & Specification Comparison

Specification	Vibeads MCP vibeads Marketing	PushEngage Marketing
Summary	Manage Google Ads from Claude: read metrics, draft campaigns, publish with human approval.	Send push notifications, build audiences, and view campaign analytics from PushEngage.
Category & Scope	Marketing	Marketing

Tools & Capabilities Breakdown

Vibeads MCP Tools (14)

list_campaigns

Enumerate all campaigns with status, budget, category

get_campaign_details

Deep dive on one campaign: metrics, ad groups, targeting, landing pages, diagnostics

get_account_health_score

0-100 score + letter grade across 6 dimensions, optionally per-campaign

get_search_term_analysis

Wasted spend + winners from each campaign's latest synced search terms, which cover the 7 days before that sync (configurable cost threshold)

get_diagnostics

Latest agent-optimize diagnostics with severity + recommended fix (up to 50)

generate_strategy

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Vibeads MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-335": {
      "command": "npx",
      "args": [
        "-y",
        "@vibeads/mcp"
      ],
      "env": {
        "VIBEADS_API_KEY": "YOUR_VIBEADS_API_KEY_HERE"
      }
    }
  }
}

PushEngage Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pushengage": {
      "command": "npx",
      "args": [
        "-y",
        "@pushengage/mcp"
      ],
      "env": {
        "PE_MCP_CLIENT_NAME": "YOUR_PE_MCP_CLIENT_NAME_HERE",
        "PE_MCP_CONFIG_PATH": "YOUR_PE_MCP_CONFIG_PATH_HERE"
      }
    }
  }
}

Frequently Asked Questions

Vibeads MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, PushEngage belongs to Marketing using local stdio subprocess. Select Vibeads MCP when you need capabilities focused on marketing and PushEngage when you require tools for marketing.