---
type: "synthesis"
spans_days: [1, 2, 3, 4, 5, 6]
tags: ["mcp", "architecture", "tool-use"]
id: "arc-mcp-connective-tissue"
sources: ["cross-day"]
---
## What this arc tracks

The **Model Context Protocol** appears in some form in every single day of the series. It is the architectural primitive that turns Claude from a text generator into an autonomous content engine. Across all six videos, MCP (or an MCP-equivalent webhook) is the seam between Claude and the outside world.

## How each day uses MCP

- **Day 1 (Alex):** [[concept-higgsfield-mcp]] — Claude calls Higgsfield's image/video generators directly inside the chat. Setup: [[action-install-higgsfield-mcp]].
- **Day 2 (CCC):** [[concept-webhook-integration]] — not strictly MCP, but the same architectural pattern. Claude triggers n8n via HTTP POST when it can't perform a task natively (audio transcription via [[concept-audio-transcription-workaround]]).
- **Day 3 (Sabrina):** [[concept-mcp]] — Perplexity MCP for fact-checking ([[entity-product-perplexity]]), Blotato MCP for scheduling ([[entity-product-blotato]]), Chrome MCP for screenshots.
- **Day 4 (MAG):** [[concept-custom-connectors-mcp]] — Blotato MCP at `https://mcp.blotato.com/mcp` exposes visual generation and multi-platform scheduling ([[action-connect-blotato-api]]).
- **Day 5 (Tim):** Claude Code talks to Arvow ([[tool-arvow]]) and Blotato ([[tool-blotato]]) via API (functionally MCP-like, possibly raw HTTP).
- **Day 6 (Dara):** Chrome connector ([[prereq-chrome-connector]]) lets [[concept-claude-cowork|Cowork]] visually read DOM pages that block direct fetching.

## The three abstraction strata

MCP is doing different work at different layers:

1. **Generation MCPs** — call out to specialized model providers. Higgsfield (Day 1), Whisper-via-Groq (Day 2), Perplexity (Day 3), Nano Banana 2 via Blotato (Day 4).
2. **Action MCPs** — execute side effects in external systems. Blotato scheduling (Days 3, 4, 5), Arvow publishing (Day 5), Notion writes (Day 2).
3. **Sensor MCPs** — let Claude read state from authenticated systems. Chrome/Claude-in-Chrome (Days 2, 6), local filesystem reads (Days 3, 4, 5).

## The unstated payoff

None of the speakers say it directly, but the unified picture is: **MCP collapses the "copy-paste between tools" tax that has dominated AI content workflows since 2022.** Once Claude can both *author* a generation prompt and *execute* it inside the same conversation, the marginal cost of a multi-step workflow approaches zero — which is what enables every "replaces a team" claim in [[arc-team-replacement-overstatement]].

## The shared risk

Every MCP is a dependency. Every dependency can change pricing, change auth, change schema, or shut down. See [[arc-platform-policy-risk]] and the open question [[question-blotato-rate-limits]] for the fragility cost no speaker emphasizes.