06-reference/research

anthropic plugin marketplace brigade strategy

2026-07-21·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
pluginsbrigade-housemcp-registrydistributionevals-as-moat

Anthropic's plugin/MCP marketplace direction and how RDCO's brigade-house strategy must adapt

The question

What is Anthropic's current strategic direction for its plugin/MCP marketplace (based on July 2026 signals), and how should RDCO's brigade-house plugin strategy adapt if Anthropic ships a native plugin discovery catalog? Context: surfaced from an orphan analysis doc whose premise (brigade value partly rests on RDCO controlling skill discovery/routing) needed a web reality-check.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The framing that "the brigade house's value partially depends on RDCO controlling skill discovery and routing" is the part of the orphan doc's premise that the web reality-check retires. A native catalog does not, and structurally cannot on current evidence, erode the brigade-house moat — because the moat was misdescribed. Anthropic's catalog answers "which plugin exists and is it safe to install" (catalog-level discovery + security verification). It does not answer "does this plugin actually work, and does it work in this client's environment against their systems." Those two questions are exactly the brigade house's two gates: eval-gated shipping with per-fixture lift evidence (works at all) and mise declared-deps/reachability/version-stamp onboarding gates (works HERE). Neither is a discovery feature, so a discovery catalog leaves both untouched. The 2026-07-09 doc's own "two halves of trust" synthesis already had this right; the web just confirms Anthropic is not competing on either half.

Where the catalog should change RDCO behavior is at the top of the funnel, not the moat. RDCO should stop treating a self-owned public discovery surface as a differentiator — that game is over, Anthropic ships 200+ plugins pre-configured out of the box, and no third-party catalog will out-distribute the in-app /plugin Discover screen. The correct adaptation is to ride Anthropic's rails for reach and keep the private center for delivery-grade proof: (1) list eligible public ray-plugins in the community marketplace and pursue the "Anthropic Verified" badge — it is cheap credibility and a security-trust signal, but explicitly not the moat, so market it as table stakes, not as the sell; (2) keep RayDataCo/brigade-house as the private dev home and the manufacturing floor where evals + mise gates produce delivery-grade artifacts (architecture documented in [[2026-07-18-agent-brigade-v2-simplification-design]]); (3) preserve intra-plugin routing (MENU + router skill) as RDCO-owned — Anthropic's discovery is catalog-level (pick a plugin), its only router (smb-router) is nascent and hand-authored, and situation→skill routing inside a delivery-grade pack is a layer it is not building.

For the [[2026-06-09-caf-restructure-proposal|CAF]]/phData topology, the native catalog is essentially a non-event: enterprise distribution via private Bitbucket + strictKnownMarketplaces lockbox + seed-dir container pre-population is a separate surface Anthropic first-classes and does not fold into the public catalog. CAF's value story runs entirely on the onboarding gate (mise proving connectivity to the client's actual Snowflake/systems) and eval evidence, both of which the catalog does not provide. If anything, Anthropic's own verticalization move (legal packs, Managed Agents in customer sandboxes with private MCP) is a tailwind: it normalizes the exact "discipline pack + private connectors, run in the client's environment" shape RDCO sells — and RDCO ships it with the two gates Anthropic omits. The one genuine watch item is monetization: Anthropic has no billing layer yet, but a future paid/verified tier or a Managed-Agents-plus-vertical-plugins bundle is the plausible next move, and that is where a well-capitalized platform could eventually compress a generic-plugin business. RDCO's insulation there is the same as everywhere: sell delivery-grade proof and per-client onboarding, which is a services-and-verification moat, not a distribution moat that a platform can undercut.

Net: adapt by conceding public discovery to Anthropic entirely, riding its rails for top-of-funnel reach and its verified badge for security-trust, while doubling down on the two gates it structurally does not build (measured efficacy + per-client onboarding verification) as the actual brigade-house differentiation. The orphan doc's "adopt their surface, keep our teeth" line is the right posture; the web evidence just tightens it from prediction to fact.

Why this is in the vault

This brief closes the citation gap on the orphan 2026-07-09 plugin-ecosystem analysis by grounding its central premise against July 2026 reality, and it directly informs the brigade-house public-distribution decision (whether/how to surface ray-plugins on Anthropic's catalog + pursue the Verified badge) and the CAF/phData plugin-topology positioning — both are live, undelivered decisions.

Open follow-ups

Related

Sources

Vault:

Web: