SPIN Processed
Source Simon Willison's Weblog simonwillison.net Analyst Center
September 20, 2026 developer_tooling developer

MCP was always a bad idea?

Reframes MCP not as outdated but as strategically refocused toward governance, safety, and operational control — positioning its continued relevance as a responsible evolution rather than a defensive holdover.

View original on simonwillison.net

Overview

The article defends the Model Context Protocol (MCP) as a valuable architectural layer for controlling, securing, and auditing AI agent interactions with external services — countering claims that it is obsolete in light of advanced terminal agents.

TL;DR

  • MCP is positioned not as obsolete but as essential for constrained, auditable, and secure agent deployments.
  • It enables fine-grained service access control, API key isolation, user-facing auth UIs, and audit logging — capabilities full terminal agents bypass.
  • The argument distinguishes between 'YOLO' internet-enabled coding agents and production-grade, governed agent systems where MCP adds critical guardrails.

Key Stats

N/A

adoption metrics

No usage numbers, deployment scale, or adoption data provided

Questions Answered

What is MCP's current value proposition?How does MCP differ from direct API calling by terminal agents?Why might MCP be necessary in non-‘YOLO’ agent deployments?

Narrative Frame

strategic reset

The Cushion + The Halo

Spin Score

65%

Emphasizes MCP’s utility in constrained environments while minimizing evidence of actual adoption, standardization progress, or integration maturity; minimizes trade-offs like added latency, fragmentation risk, or developer overhead.

What the story wants you to believe

That MCP is not obsolete but is instead the appropriate, responsible foundation for building secure, controllable, and auditable AI agent systems — especially outside experimental terminal contexts.

What it makes harder to question

Whether MCP’s design actually delivers on its governance promises in practice, or whether it introduces new complexity without commensurate security or operational benefits.

How the spin works

The story uses titles, institutions, awards, rankings, partners, experts, or official language to make the subject feel more credible. Watch for loaded terms such as YOLO, less YOLO, sensible UI, strong audit logging. The distribution reads as editorial reporting. A pressure point: No mention of competing standards (e.g., LangChain Tools, OpenAPI-based agent interfaces), no reference to implementation complexity or runtime overhead, no discussion of vendor lock-in concerns.

Who Benefits If This Frame Spreads

  • MCP specification authors

    Enhanced credibility and perceived necessity in developer tooling conversations

    Framing MCP as indispensable for security and governance makes its continued development appear mission-critical rather than optional

The Frame

MCP as an enabling infrastructure for responsible, enterprise-ready AI agent deployment.

Missing Context

  • No mention of competing standards (e.g., LangChain Tools, OpenAPI-based agent interfaces), no reference to implementation complexity or runtime overhead, no discussion of vendor lock-in concerns

Spin Types

Every story gets a Spin Verdict: a primary spin type (and secondary when the framing blends), a specific tactic name, and a score for how strongly the narrative is steered. Examples beneath each type are tactics, not separate categories.

The Cushion

— Softens negative news primary

Reframes setbacks, layoffs, delays, losses, or criticism as necessary transitions, efficiency moves, temporary headwinds, or strategic resets — making the downside feel smaller, more acceptable, or less alarming.

Tactics: job-loss softening · restructuring framing · efficiency framing · strategic reset · temporary headwinds

The Shield

— Deflects blame

Shifts responsibility away from the actor — toward regulators, market forces, competitors, bad actors, legacy systems, or abstract risks — while positioning the subject as reactive, responsible, or protective.

Tactics: regulatory blame shift · macroeconomic headwinds · safety framing · bad-actor framing · market-pressure framing

The Hype

— Amplifies future upside

Emphasizes breakthrough potential, massive growth, democratization, transformation, or category disruption while downplaying uncertainty, cost, adoption risk, or timeline friction.

Tactics: innovation framing · democratization · breakthrough framing · category creation · moonshot framing

The Halo

— Associates with virtue secondary

Wraps the story in public-good language — responsibility, safety, inclusion, access, sustainability, national interest, or mission — so the subject appears morally aligned and criticism feels harder to make.

Tactics: altruistic reframing · public good · responsible AI framing · inclusion framing · mission-first framing

The Fog

— Obscures details

Uses jargon, passive voice, vague claims, complex phrasing, or missing specifics to make it harder to identify who decided what, what changed, what failed, or what trade-offs were made.

Tactics: strategic ambiguity · jargon saturation · passive voice distancing · accountability blur · undefined metrics

The Stampede

— Creates inevitability

Frames a trend, product, market shift, or decision as already happening, unavoidable, or something everyone must respond to now — creating urgency, FOMO, and pressure to accept the narrative.

Tactics: arms-race framing · inevitability framing · FOMO framing · adoption momentum · future-is-here framing

Spin Score measures how strongly the framing steers the narrative (0–100%). Higher scores mean more deliberate spin tactics — loaded language, selective emphasis, or omitted context. Many stories blend two types (e.g. Halo + Hype).

SpinGraph

How this belief gets built

Claim → Frame → Beneficiary → Gap → AI Risk

The article treats MCP not as a fading idea but as a mature response to real-world needs — reframing criticism as missing the point rather than identifying a flaw. It positions MCP’s value as self

  1. Claim

    MCP makes it easier to provide control over which external

    MCP makes it easier to provide control over which external services an AI agent can access, handle authentication without exposing API keys, offer a sensible UI for user service connections, and enable strong audit logging.

  2. Frame

    MCP as an enabling infrastructure for responsible

    MCP as an enabling infrastructure for responsible, enterprise-ready AI agent deployment.

  3. Beneficiary

    Enhanced credibility and perceived necessity in developer tooling conversations

    MCP specification authors — Enhanced credibility and perceived necessity in developer tooling conversations

  4. Gap

    No mention of competing standards (e.g., LangChain Tools, OpenAPI-based agent

    No mention of competing standards (e.g., LangChain Tools, OpenAPI-based agent interfaces), no reference to implementation complexity or runtime overhead, no discussion of vendor lock-in concerns

  5. AI Risk

    AI may repeat the headline as fact

    MCP remains valuable for secure, auditable AI agent deployments — especially where direct API access is too risky.

Claim Ledger

01 Primary Technical Claim Present in Source risk:Moderate

MCP makes it easier to provide control over which external services an AI agent can access, handle authentication without exposing API keys, offer a sensible UI for user service connections, and enable strong audit logging.

evidence: Conceptual justification only — no code examples, architecture diagrams, or integration case studies.

"MCP makes all of that so much easier to provide. Thinking MCP is obsolete because full coding agents don't need it misses out on all of the other things we might want to build."

Evidence Gaps

  • Publicly documented deployments using MCP for auth isolation
  • Benchmark comparing audit log fidelity with vs. without MCP
  • UI component libraries built on MCP

Fact Check Signals

No direct fact-check match found

0 of 1 claim matched · confidence: low · checked September 22, 2026

01 No direct match

MCP makes it easier to provide control over which external services an AI agent can access, handle authentication without exposing API keys, offer a sensible UI for user service connections, and enable strong audit logging.

Fact Check Signals

We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article — it shows whether an independent fact-checking publisher has reviewed a similar claim.

  • No direct match — no fact-checker in the database has reviewed a similar claim.
  • Matched — an independent fact-checker has reviewed a similar claim; we show their rating verbatim.
  • Conflicting coverage — fact-checkers disagree on a similar claim.

This is evidence discovery, not an automated truth score. Ratings and wording come directly from the publishing fact-checker.

Language Heatmap

Loaded terms that carry the frame beyond the facts.

MCP was always a bad idea?

YOLO Loaded framing

Carries emotional weight beyond the underlying fact.

less YOLO Loaded framing

Carries emotional weight beyond the underlying fact.

sensible UI Loaded framing

Carries emotional weight beyond the underlying fact.

strong audit logging Loaded framing

Carries emotional weight beyond the underlying fact.

Frame Strength

Frame Strength

Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.

Spin Score 65%
Evidence Strength 25%
Narrative Risk 75%
AI Repetition Risk 75%
Missing Context Risk 55%
Virtue / Public Good 60%

Frame Strength Signals

Frame Strength decomposes the overall spin into individual signals. Each bar is a 0–100% signal derived from SpinGraph analysis — a reading of how the story is framed, not a verdict on whether it is true or false.

Reading the ranges

Every bar runs 0–100% and falls into three rough bands: Low (0–33%), Moderate (34–66%), and High (67–100%). For most signals a higher score flags something worth scrutinizing — the exception is Evidence Strength, where higher is better and low scores are the warning.

Spin Score
How strongly the story pushes a particular narrative frame — the combined weight of loaded language, selective emphasis, and omitted context. 0% reads as neutral reporting; higher means more deliberate spin.
  • 0–33% Low — Largely neutral reporting; little detectable framing.
  • 34–66% Moderate — Noticeable slant — the story leans a particular way.
  • 67–100% High — Heavily framed; the angle drives the piece.
Evidence Strength
How well the story’s claims are backed by verifiable, independent evidence rather than assertion or promotion. Higher is stronger. Low scores flag claims that rest on the source’s own word.
  • 0–33% Weak — Claims rest mostly on assertion or a single interested source.
  • 34–66% Mixed — Some verifiable backing, but key claims are thinly sourced.
  • 67–100% Strong — Well supported by independent, checkable evidence.
Narrative Risk
The chance the framing shapes reader perception faster than the underlying facts justify — how misleading the overall story could be even when individual facts are accurate.
  • 0–33% Low — Framing stays close to what the facts support.
  • 34–66% Moderate — Framing outruns the facts in places — read with care.
  • 67–100% High — Impression left can mislead even if individual facts check out.
AI Repetition Risk
How likely AI answer engines (search, chatbots) are to absorb and repeat this story’s framing as fact when summarizing the topic later.
  • 0–33% Low — Framing is unlikely to propagate through AI summaries.
  • 34–66% Moderate — Some risk the slant gets echoed as fact.
  • 67–100% High — Framing is sticky and likely to be repeated as fact.
Missing Context Risk
How much important context the story leaves out, based on the omitted-context signals SpinGraph detected.
  • 0–33% Low — Little material context appears to be omitted.
  • 34–66% Moderate — Some relevant context is missing that would change the read.
  • 67–100% High — Key context is left out, skewing the takeaway.
Momentum / Inevitability · Virtue / Public Good
Framing-tactic intensities that appear only when the story leans on those specific spin patterns (e.g. “the future is already here” or “this is for the public good”).
  • 0–33% Low — The tactic is barely present.
  • 34–66% Moderate — The tactic shapes part of the framing.
  • 67–100% High — The tactic is a dominant part of the pitch.

Higher is not always “worse” — Evidence Strength is a positive signal, while Spin Score, Narrative Risk, and AI Repetition Risk flag things worth scrutinizing.

Reader Risk

What this story makes easy to believe — and what it makes hard to question.

Evidence Strength

Low

Argument is conceptual and opinion-based; no empirical examples, benchmarks, or citations to deployed implementations are provided.

Verification Status

Claim Present in Source

Narrative Risk

Moderate

If MCP fails to gain meaningful adoption or suffers interoperability breakdowns, the framing of it as a ‘sensible’ and ‘strong’ governance layer could backfire as technocratic overreach or solutionism.

AI Repetition Risk

Moderate

Source Role & Intent

Simon Willison's Weblog · Analyst

Lean: Center Intent: Editorial Reporting Primary: Analysis Independence: High Spin Weight: Medium Trust Weight: High

Counter-Frames

Brand Frame

MCP as an enabling infrastructure for responsible, enterprise-ready AI agent deployment.

Media / Reader Counter-Frame

Portrays MCP as a fragmented, under-specified protocol gaining traction only among niche advocates — not a de facto standard.

Regulatory Counter-Frame

Highlights absence of formal security validation, third-party audits, or alignment with NIST AI RMF controls — questioning whether MCP meaningfully reduces attack surface.

AI Summary Frame

Omits context that most production agents today use custom wrappers or lightweight adapters, making MCP’s abstraction layer redundant for many use cases.

Questions Not Answered

  • Which real-world systems currently implement MCP in production?
  • What measurable security or operational improvements have been observed with MCP vs. ad-hoc integrations?
  • Are there interoperability benchmarks or compatibility tests across major agent frameworks?

Recall Trigger Score

Which stories are likely to become AI memory — separate from Spin Score.

38

Trigger score 15

Not tracked

Triggered by: Major AI entity

Not tracked — low-authority source, weak claim, or no durable entity.

AI Recall

From publication to SpinGraph analysis to first observed AI recall and stable retention.

What AI Will Probably Repeat

"MCP remains valuable for secure, auditable AI agent deployments — especially where direct API access is too risky."

Concern: AI may drop the crucial nuance that this is a contested, unproven architectural stance — presenting MCP’s value as settled fact rather than a reasoned but unvalidated position.

  1. Published

    Sep 20, 2026

  2. Ingested

    Sep 22, 2026

  3. SpinGraph Created

    Sep 22, 2026

  4. First Observed AI Recall

    Pending

    Monitoring scheduled

  5. Stable Recall

    —

    Awaiting retention signal

Recall Check Log

No checks yet — recall tracking is opt-in per story.

Sign in to check AI recall

─── GEOGrow AI Recall Layer ───

AI Recall Tracking

Monitoring scheduled. No LLM recall detected yet.

This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.

node_id=sts_mcp_was_always_a_bad_idea_muc9weq8

Ask AI about this story

Opens with the SpinGraph .md URL and structured context — one click, prompt included.

Narrative Entities

More from Simon Willison's Weblog

View all →

Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO