The argument in one line.
AI agents become exponentially more useful when given access to external tools through Claude Projects and Docker, which lets you automate complex workflows like content creation by combining Notion databases, AI image generation, and web search into a single orchestrated system.
Read if. Skip if.
- A solo creator or small team running content operations who wants to automate repetitive tasks like thumbnail generation, database management, or content organization without hiring engineers.
- Someone building a product or service who needs to understand how AI agents with tools actually work in practice, beyond the MCP buzzword, through a concrete working example.
- A non-technical founder or operator who wants to see how Claude Projects can orchestrate multiple tools and databases to handle workflow automation at scale.
- You're already comfortable building AI agents in code or have a technical team — this is specifically designed for non-technical setup and understanding, not advanced implementation.
- You need a production-ready, fully polished system today — the video explicitly acknowledges the current setup is janky and still evolving.
- You're working with fiction, creative writing, or domains where AI agents with database-connected tools aren't directly applicable to your workflow.
The full version, fast.
MCP is a distracting buzzword for what actually matters: giving AI models tools they can use in a loop, which is the working definition of an agent. The mechanism shown is Claude Sonnet or Opus connected through Docker's MCP toolkit to external tools � Notion for context-aware content workflows and Glif for remixable mini-workflows like thumbnail generation � wrapped inside a Claude Project whose system prompt tells the agent which databases to read, where to comment, and which glyphs to invoke. The practical conclusion is to stop building n8n workflows from scratch and instead remix existing ones, curate a library of strong examples to feed the agent, scope each integration's access narrowly, and accept the current jank because the leverage compounds as tooling matures.
Chat with this breakdown.
Modern Creator members can chat with any breakdown — ask for the hook, quote a framework, find the exact transcript moment. Unlocks at T2: refer 3 friends + add your own API key.
Create a free account →Who's talking.
Where the time goes.

01 · Intro & teaser
Greg solos to camera, frames the MCP promise and difficulty of setup, introduces Riley Brown.

02 · MCP = agents with tools
Riley strips the buzzword. Defines AI agents as models using tools in a loop. Introduces n8n. Uses Anthropic definition slide.

03 · Why tools matter
Perplexity built $1B on one tool. Cursor is Claude with code-search tools. Boring Marketer applies same pattern to content creation.

04 · IdeaBrowser ad read
Sponsored mid-roll for ideabrowser.com.

05 · Docker MCP Toolkit
116-tool catalog. Riley shows Notion and Glif integrations enabled. More tools without matching instructions = confusion.

06 · Notion + Claude live demo
Riley demos querying his Agent Mind Notion workspace, pulling short-form hook structures, searching web for Dia browser, generating three content options, writing entries back to Content Database — all in one Claude chat.

07 · Claude artifacts vs MCP + Glif intro
Greg asks about artifacts. Riley explains artifacts as a render layer, distinct from MCP tools. Transition to Glif.

08 · Glif thumbnail workflow demo
Riley shows Glif.app — visual workflow builder, no API keys needed, public + remixable. Runs Thumbnail Ideator from Claude via MCP. Uses PDF of example thumbnails as style reference. Outputs five options on a canvas.

09 · Becoming the AI orchestrator
Riley shows VibeCode CEO Claude Project — system prompt referencing Notion for rules, [[double bracket]] triggers for Glif workflows. Human role becomes quarterback.

10 · Janky now, inevitable soon + VibeCode pitch
Honest take on current friction. Riley argues leverage comes from building with janky tools before they are smooth. VibeCode one-liner close.
Lines worth screenshotting.
- MCP is a buzzword — the actual concept underneath it is simply agents with tools, which is all you need to understand.
- AI agents are models using tools in a loop; they decide what tools to use and for how long, which is why they are not the same as automations.
- Perplexity built a billion-dollar company by adding exactly one tool to an AI model — the ability to search the internet before responding.
- Cursor is so powerful because it wrapped a familiar model with the right tools; the model itself is the same Claude everyone else uses.
- Giving Claude access to your Notion database as a tool means it can generate content with real context instead of hallucinated context.
- Most non-technical people can build powerful AI agents today using N8N because it makes the agent decision loop visual.
- The gap between people consuming AI and people building with AI is the same gap that has always existed between audiences and creators.
Build your Agent Mind now, while the tools are janky.
The window to build a content workflow that compounds is open right now — precisely because most people are waiting for it to be easier.
- Create an Agent Instructions document written for the AI, not for humans. This is your context moat.
- Pick two MCP tools max to start: one for knowledge base (Notion, Obsidian) and one for output layer (Glif, or a script).
- Set up a Claude Project as your orchestrator. Give it your rules, triggers, and voice.
- Build a hooks/examples database and give AI access to it. The database is the edge.
- Steal Riley's double-bracket trigger pattern for firing specific workflows mid-chat.
- JoeFlow framing: Sessions + Chef = the same orchestrator pattern, native to the desktop. Pitch: you already know this works — here it is without Docker.
Terms worth knowing.
- MCP (Model Context Protocol)
- An open standard for connecting external tools and data sources to large language models. It lets a chat assistant call outside services like Notion or a web scraper instead of being limited to its training data.
- AI agent
- A language model that uses tools in a loop, deciding on its own which tools to call and for how long until a task is finished. Different from a fixed automation because the steps are chosen at runtime, not pre-wired.
- n8n
- A visual workflow automation platform similar to Zapier where users chain triggers, conditional logic, and AI agent nodes together. Popular for building no-code agent workflows.
- Zapier
- A no-code automation service that connects apps through pre-built triggers and actions, used as the reference point for how integration marketplaces work.
- Claude Sonnet 4 / Claude Opus 4
- Two tiers of Anthropic's Claude model family used as the underlying agent. Sonnet is the faster mid-tier and Opus is the most capable, both designed to handle tool use natively.
- Cursor
- An AI-powered code editor built on top of VS Code that wraps Claude with tools for searching the codebase and the web. Used here as an example of an agent made powerful by its toolset.
- Docker MCP Toolkit
- A catalog inside Docker Desktop that exposes pre-packaged MCP servers, letting users enable external tools for an AI chat app without setting up each integration by hand.
- MCP server
- The background process that exposes a given tool's capabilities to the AI model over MCP. It must be running locally for the chat app to see and call its tools.
- Composio
- A platform that aggregates third-party integrations and exposes them to AI agents, positioned as an alternative way to add tools beyond Docker's catalog.
- Firecrawl
- A web scraping and crawling service that can be wired into an agent as a search-the-internet tool. Requires its own API keys to configure.
- Glif
- A no-code workflow builder where users assemble chains of AI models and image steps into reusable mini-apps. Each workflow can be called as a tool from inside Claude via MCP.
- Notion integration token
- A secret key generated inside Notion's developer settings that grants an external app or AI agent permission to read and write specific pages in a workspace.
- Claude Artifacts
- A Claude feature that renders generated content like code, landing pages, or diagrams in a side panel of the chat. Comparable to OpenAI's Canvas and Gemini's Canvas.
- Mermaid diagram
- A lightweight text-based language for describing flowcharts, sequence diagrams, and other visuals that get rendered into images. Useful for letting an AI produce diagrams as code.
- Claude Project
- A workspace inside Claude where users save custom system instructions, files, and rules that apply to every chat in that project. Used here to give an agent a persistent role and toolset.
- System prompt
- The hidden set of instructions given to a language model before the user's message that shapes its behavior, persona, and tool-use rules across a conversation.
- ComfyUI
- A node-based interface for building generative image pipelines, referenced as the kind of complex visual workflow builder Glif was initially mistaken for.
- Vibe coding
- Building software by describing what you want in natural language to an AI rather than writing code by hand. The term has expanded into adjacent areas like vibe marketing.
- SOP (Standard Operating Procedure)
- A documented set of repeatable steps for performing a task, stored here in Notion so an AI agent can read and follow the same process a human team would.
- BYOK (Bring Your Own Key)
- A model where the user supplies their own API keys for each underlying service the tool calls, instead of paying a single bundled subscription. Common pain point when wiring up many MCP integrations.
Things they pointed at.
Lines you could clip.
“AI agents are models using tools in a loop.”
“Perplexity built a billion dollar company adding one single tool.”
“Most of the leverage from these tools comes from doing things when they're janky and bad, understanding that it's not going to be janky and bad.”
“Anthropic, I know you're watching. Plug it into the platform. It'd be great.”
“I want to hire someone full time and all they do is just pull really good examples.”
Where the conversation goes.
Word for word.
The bait, then the rug-pull.
The hook is a permission structure: Greg admits he does not know how this works yet, which gives every non-technical viewer cover to keep watching. Riley Brown enters as the explainer, armed with a live Claude session and a Notion workspace he has literally written for AI agents to navigate. By minute eight, the buzzword is dead and the demo has begun.






































































