NotFair vs Timothe's Growth Calendar

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

NotFair logoNotFairMarketing · Remote HTTP/SSEGoogle Ads MCP - analyze performance, manage keywords, bids, and campaigns.49FairAuth: oauth 2.0Timothe's Growth Calendar logoTimothe's Growth CalendarMarketing · Remote HTTP/SSEPlan, schedule and generate SEO articles on a content calendar, from your agent.36FairAuth: not declared

Verdict: choose NotFair for marketing work over a hosted endpoint; choose Timothe's Growth Calendar for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

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

Timothe's Growth Calendar logoChoose Timothe's Growth Calendar when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore Timothe's Growth Calendar

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNotFair logoNotFairTimothe's Growth Calendar logoTimothe's Growth Calendar
CategoryMarketingMarketing
Quality signal49/100 · Fair36/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars4,0550
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

NotFair tools

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

Timothe's Growth Calendar 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.

NotFair

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

Timothe's Growth Calendar

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "timothe-s-growth-calendar": {
      "url": "https://timothe.ai/mcp/growth-calendar"
    }
  }
}

Frequently asked questions

NotFair is categorized under Marketing and uses a remote HTTP/SSE transport. Timothe's Growth Calendar belongs to Marketing and uses a remote HTTP/SSE transport. Pick NotFair for marketing work and Timothe's Growth Calendar 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.

NotFair has no declared pricing — check the project's own site. Auth: oauth 2.0. Timothe's Growth Calendar has no declared pricing — check the project's own site. 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 notfair and timothe-s-growth-calendar as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, NotFair has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 4,055 GitHub stars. Timothe's Growth Calendar has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.