Log inSubmit server

ClearPost: WordPress SEO Agent vs NotFair GoogleAds

A side-by-side look at the ClearPost: WordPress SEO Agent 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
ClearPost: WordPress SEO AgentMarketing · Remote HTTP/SSESEO agent for WordPress. Grows your organic traffic on autopilot. 12 tools, zero configuration.42FairAuth: 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 ClearPost: WordPress SEO Agent 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 ClearPost: WordPress SEO Agent when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore ClearPost: WordPress SEO Agent

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
ClearPost: WordPress SEO Agent		NotFair GoogleAds logoNotFair GoogleAds
CategoryMarketingMarketing
Quality signal42/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—4,055
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView ClearPost: WordPress SEO Agent View NotFair GoogleAds

Tools & capabilities

ClearPost: WordPress SEO Agent 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.

ClearPost: WordPress SEO Agent

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "clearpost-wordpress-seo-agent": {
      "url": "https://clearpostplugin.com/mcp"
    }
  }
}

NotFair GoogleAds

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

Frequently asked questions

ClearPost: WordPress SEO Agent is categorized under Marketing and uses a remote HTTP/SSE transport. NotFair GoogleAds belongs to Marketing and uses a remote HTTP/SSE transport. Pick ClearPost: WordPress SEO Agent 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.

ClearPost: WordPress SEO Agent 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 clearpost-wordpress-seo-agent and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ClearPost: WordPress SEO Agent has a quality signal of 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. NotFair GoogleAds has 49/100 (Fair) with 1 views, 0 installs and 4,055 GitHub stars.

Popular comparisons with ClearPost: WordPress SEO Agent

Popular comparisons with NotFair GoogleAds