Marketscore Direct MCP vs NotFair GoogleAds

A side-by-side look at the Marketscore Direct 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.

Marketscore Direct MCP logoMarketscore Direct MCPMarketing · Local subprocess (stdio)MCP for Yandex Direct: manage ad campaigns & analytics from Claude or ChatGPT40FairAuth: not declaredNotFair 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 Marketscore Direct MCP for marketing work as a local process; 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?

Marketscore Direct MCP logoChoose Marketscore Direct MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
Explore Marketscore Direct 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.

SpecMarketscore Direct MCP logoMarketscore Direct MCPNotFair GoogleAds logoNotFair GoogleAds
CategoryMarketingMarketing
Quality signal40/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars24,040
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Marketscore Direct 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.

Marketscore Direct MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "marketscore-direct-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "marketscore-direct-mcp"
      ]
    }
  }
}

NotFair GoogleAds

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

Frequently asked questions

Marketscore Direct MCP is categorized under Marketing and uses a local stdio subprocess. NotFair GoogleAds belongs to Marketing and uses a remote HTTP/SSE transport. Pick Marketscore Direct 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.

Marketscore Direct MCP has no declared pricing — check the project's own site. 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 marketscore-direct-mcp and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Marketscore Direct MCP has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 4,040 GitHub stars.