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

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

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

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

Which MCP server has more tools and community activity?

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

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

Meta Ads MCP vs Revup

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

Meta Ads MCP

Marketing · Local stdio

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

Revup

Marketing · Remote HTTP/SSE

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

Verdict Summary: Choose Meta Ads MCP if you need specialized Marketing tools running via a local process. Choose Revup if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

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

Feature & Specification Comparison

Specification	Meta Ads MCP mikusnuz Marketing	Revup VerifiedMarketing
Summary	MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.	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.
Category & Scope

Tools & Capabilities Breakdown

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.

copy_campaign

Copy an existing campaign. Creates a duplicate with optional name override. Copies structure including ad sets and ads.

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

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"
      }
    }
  }
}

Revup Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Meta Ads MCP More alternatives to Revup Marketing category hub