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

Convika belongs to the Marketing category with local stdio execution, while Meta Ads MCP belongs to the Marketing category with local stdio execution.

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

Convika operates under a Free / Open Source model (No auth required). Meta Ads MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Convika lists 5 tools with 3 views and 0 GitHub stars. Meta Ads MCP lists 134 tools with 1 views and 79 GitHub stars.

Can I use both Convika 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

Convika vs Meta Ads MCP

In-depth architectural comparison of the Convika 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

Convika

Marketing · Local stdio

Quality: 37/100 (Fair) | Auth: No auth required

Meta Ads MCP

Marketing · Local stdio

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

Verdict Summary: Choose Convika if you need specialized Marketing tools running via a local process. 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 Convika 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).
Primary tools included: Landing-page creation, Landing-page previews, Landing-page publishing.

Explore Convika 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.

Feature & Specification Comparison

Specification	C Convika Marketing	Meta Ads MCP mikusnuz Marketing
Summary	Create, preview, publish, and measure landing pages from Claude, Codex, or any MCP client.	MCP server for Meta Marketing API v25.0 — 123 tools for Facebook & Instagram ad campaigns, audiences, creatives, insights, catalogs, and automated rules.
Category & Scope	Marketing	Marketing

Tools & Capabilities Breakdown

Convika Tools (5)

Landing-page creation

Landing-page previews

Landing-page publishing

Landing-page measurement

MCP client access

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.

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

Convika Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "convika": {
      "command": "npx",
      "args": [
        "-y",
        "convika"
      ]
    }
  }
}

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

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

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