What is the key difference between Revup and Meta Ads MCP?

Revup belongs to the Marketing category with cloud HTTP/SSE execution, while Meta Ads MCP belongs to the Marketing category with local stdio execution.

How do I install Revup or Meta Ads MCP 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 Revup and Meta Ads MCP free or paid?

Revup operates under a Freemium model (OAuth 2.0). Meta Ads MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Revup lists 0 tools with 1 views and 0 GitHub stars. Meta Ads MCP lists 134 tools with 1 views and 82 GitHub stars.

Can I use both Revup and Meta Ads MCP 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

Revup vs Meta Ads MCP

In-depth architectural comparison of the Revup and Meta Ads MCP 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

Revup

Marketing · Remote HTTP/SSE

Quality: 65/100 (Great) | Auth: OAuth 2.0

Meta Ads MCP

Marketing · Local stdio

Quality: 65/100 (Great) | Auth: API Key required

Verdict Summary: Choose Revup if you need specialized Marketing tools running via a hosted cloud SSE transport. Choose Meta Ads MCP 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 Revup when:

You need dedicated capabilities in the Marketing domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).

Explore Revup Details

Choose Meta Ads MCP when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: META_ADS_ACCESS_TOKEN, META_AD_ACCOUNT_ID, META_APP_ID, META_APP_SECRET, META_BUSINESS_ID, META_PIXEL_ID.
Primary tools included: list_campaigns, get_campaign, create_campaign.

Explore Meta Ads MCP Details

Feature & Specification Comparison

Specification	Revup VerifiedMarketing	Meta Ads MCP mikusnuz Marketing
Summary	Create, customize, preview and report on sweepstakes, contests, forms, surveys, quizzes and other promotions in a connected Revup account. Connect through OAuth; access follows your account role and granted permissions.	MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.
Category & Scope

Tools & Capabilities Breakdown

Revup Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Meta Ads MCP Tools (134)

list_campaigns

List campaigns in the ad account. Supports filtering by status and objective. Returns paginated results.

get_campaign

Get details of a specific campaign by ID.

create_campaign

Create a new ad campaign. Defaults to PAUSED status. Requires name and objective. Budget can be set at campaign or ad set level.

update_campaign

Update an existing campaign. Only provided fields will be modified.

delete_campaign

Delete a campaign. This action is irreversible.

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).

Revup Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "revup": {
      "url": "https://revup.com/docs/mcp/"
    }
  }
}

Meta Ads MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mikusnuz-meta-ads-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-ads-mcp"
      ],
      "env": {
        "META_ADS_ACCESS_TOKEN": "YOUR_META_ADS_ACCESS_TOKEN_HERE",
        "META_AD_ACCOUNT_ID": "YOUR_META_AD_ACCOUNT_ID_HERE",
        "META_APP_ID": "YOUR_META_APP_ID_HERE",
        "META_APP_SECRET": "YOUR_META_APP_SECRET_HERE",
        "META_BUSINESS_ID": "YOUR_META_BUSINESS_ID_HERE",
        "META_PIXEL_ID": "YOUR_META_PIXEL_ID_HERE"
      }
    }
  }
}

Frequently Asked Questions

Revup is categorized under Marketing and uses a remote streaming HTTP/SSE transport. In contrast, Meta Ads MCP belongs to Marketing using local stdio subprocess. Select Revup when you need capabilities focused on marketing and Meta Ads MCP when you require tools for marketing.

More alternatives to Revup More alternatives to Meta Ads MCP Marketing category hub Canonical compare URL