Moonlings — Local Business Intelligence vs NotFair

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

M
Moonlings — Local Business IntelligenceMarketing · Remote HTTP/SSE
AI visibility checks, review gaps, competitor scans, and deep research for local businesses.42FairAuth: not declared
NotFair logoNotFairMarketing · Remote HTTP/SSEGoogle Ads MCP - analyze performance, manage keywords, bids, and campaigns.49FairAuth: oauth 2.0

Verdict: choose Moonlings — Local Business Intelligence for marketing work over a hosted endpoint; choose NotFair for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

M
Choose Moonlings — Local Business Intelligence when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore Moonlings — Local Business Intelligence

NotFair logoChoose NotFair 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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
M
Moonlings — Local Business Intelligence
NotFair logoNotFair
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,040
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Moonlings — Local Business Intelligence tools

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

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

Moonlings — Local Business Intelligence

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "moonlings-local-business-intelligence": {
      "url": "https://moonlings.ai/mcp"
    }
  }
}

NotFair

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

Frequently asked questions

Moonlings — Local Business Intelligence is categorized under Marketing and uses a remote HTTP/SSE transport. NotFair belongs to Marketing and uses a remote HTTP/SSE transport. Pick Moonlings — Local Business Intelligence for marketing work and NotFair 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.

Moonlings — Local Business Intelligence has no declared pricing — check the project's own site. NotFair 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 moonlings-local-business-intelligence and notfair as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Moonlings — Local Business Intelligence has a quality signal of 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. NotFair has 49/100 (Fair) with 2 views, 0 installs and 4,040 GitHub stars.