Appfigures vs NotFair

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

Appfigures logoAppfiguresMarketing · Local subprocess (stdio)Access your app analytics, ASO tools, and app market intelligence with Appfigures.48FairAuth: not declaredNotFair logoNotFairMarketing · Remote HTTP/SSEGoogle Ads MCP - analyze performance, manage keywords, bids, and campaigns.49FairAuth: oauth 2.0

Verdict: choose Appfigures for marketing work as a local process; 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?

Appfigures logoChoose Appfigures when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: APPFIGURES_API_KEY.
Explore Appfigures

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.

SpecAppfigures logoAppfiguresNotFair logoNotFair
CategoryMarketingMarketing
Quality signal48/100 · Fair49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsAPPFIGURES_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars203,970
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

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

Appfigures

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "appfigures": {
      "command": "npx",
      "args": [
        "-y",
        "@appfigures/cli"
      ],
      "env": {
        "APPFIGURES_API_KEY": "YOUR_APPFIGURES_API_KEY_HERE"
      }
    }
  }
}

NotFair

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

Frequently asked questions

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

Appfigures 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 appfigures and notfair as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Appfigures has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 20 GitHub stars. NotFair has 49/100 (Fair) with 1 views, 0 installs and 3,970 GitHub stars.