ClipMyApp MCP vs NotFair GoogleAds

A side-by-side look at the ClipMyApp MCP and NotFair GoogleAds MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

C
ClipMyApp MCPMarketing · Remote HTTP/SSE
Hosted MCP server for app founders and marketing teams to create, review, edit, approve or reject, and schedule app videos, memes, and carousels from AI assistants. Scoped OAuth and explicit confirmation keep publishing and spend under the account owner control.50GoodAuth: oauth 2.0
NotFair GoogleAds logoNotFair GoogleAdsMarketing · Remote HTTP/SSEHosted Google Ads MCP with OAuth, 117 tools, MCC routing, image assets, and approval-gated writes.49FairAuth: oauth 2.0

Verdict: choose ClipMyApp MCP for marketing work over a hosted endpoint; choose NotFair GoogleAds for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

C
Choose ClipMyApp MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore ClipMyApp MCP

NotFair GoogleAds logoChoose NotFair GoogleAds when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore NotFair GoogleAds

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
C
ClipMyApp MCP
NotFair GoogleAds logoNotFair GoogleAds
CategoryMarketingMarketing
Quality signal50/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthOAuth 2.0OAuth 2.0
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—4,057
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

ClipMyApp MCP tools

No tool names declared yet. Check the project README from the listing page.

NotFair GoogleAds 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.

ClipMyApp MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "clipmyapp-mcp": {
      "url": "https://api.clipmyapp.com/mcp"
    }
  }
}

NotFair GoogleAds

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "notfair-googleads": {
      "url": "https://notfair.co/api/mcp/notfair"
    }
  }
}

Frequently asked questions

ClipMyApp MCP is categorized under Marketing and uses a remote HTTP/SSE transport. NotFair GoogleAds belongs to Marketing and uses a remote HTTP/SSE transport. Pick ClipMyApp MCP for marketing work and NotFair GoogleAds 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.

ClipMyApp MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. NotFair GoogleAds has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 clipmyapp-mcp and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ClipMyApp MCP has a quality signal of 50/100 (Good) with 2 views, 0 installs and 0 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 4,057 GitHub stars.