Ext Ops Panel
Open dashboard
Comparison

gtm-engineering-command-center vs NotFair

gtm-engineering-command-center is a plugin bundle for AI coding tools published by Dojo Coding Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). NotFair is an MCP server published by nowork-studio. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegtm-engineering-command-centerNotFair
Community marketplace dojocodinglabs/gtm-engineering-command-center Listed
Version: 1.14.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.27.16
Forks (GitHub): 495
Stars (GitHub): 3 945
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

gtm-engineering-command-center vs NotFair
Factgtm-engineering-command-centerNotFair
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub3 945
Forks (GitHub) (differs)No figure on GitHub495
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleRemote server (notfair.co/api/mcp/notfair)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)6549
LicenceMITMIT
Repository (differs)github.com/dojocodinglabs/gtm-engineering-command-centergithub.com/nowork-studio/notfair-plugin
Changes in the last 7 days (differs)26
First seen (differs)2026-10-162026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 40 h ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

gtm-engineering-command-center

In its own words, on Community GitHub marketplaces:

Autonomous GTM operating system — 16 agents, 30 commands, 17 skills. Multichannel orchestration (Meta Ads + Google Ads at parity), AARRR funnel diagnostics, Tribe v2 neural pre-testing, Synthetic Demand Validation (SDV) for demand/price/objection pre-testing with a unified neuro+SDV pre-flight gate and pricing science, the High-Velocity Advertising (HVA) engine (CLEAR + deterministic scorer + the Vault moat), browser QA, cross-channel attribution, codebase-aware asset generation, and cloud Routines.

NotFair

In its own words, on Official MCP Registry:

OAuth MCP for Google, Meta, X, LinkedIn, Reddit, TikTok, GSC, GA4, WordPress and GHL.

How to run each

gtm-engineering-command-center As a Claude Code plugin

Claude Code
/plugin marketplace add dojocodinglabs/gtm-engineering-command-center
/plugin install gtm-engineering-command-center@gtm-engineering-command-center

NotFair As a remote MCP server

Claude Code
claude mcp add --transport http notfair https://notfair.co/api/mcp/notfair

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only NotFair has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: gtm-engineering-command-center · What it can do: NotFair · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built