MCP Tutorial: Connect AI to your HomeLab (and more…)
MCP Tutorial: Connect AI to your HomeLab (and more…)
This allows YouTube videos and product images hosted on Amazon. YouTube may set cookies when a video loads. Read the privacy policy
Watch on YouTube instead (opens in a new tab)Video write-up
In this video, I show how to connect AI to your HomeLab, DevOps workflows, and external tools using the Model Context Protocol (MCP), including practical examples with GitHub, Cloudflare, n8n, and more.
Up next
More videos with similar topics.
My BEST N8N HomeLab automations (AI Agents…)
In this video, I show my best n8n HomeLab automation workflows built with AI agents, including automated service updates with patchnote analysis and server health monitoring. Notes Practical tips: Define strict JSON schema for AI outputs t…
A Better Way to Run Terminal Agents!
Is Herdr a better way to manage terminal agents? I put its workspaces, Git worktrees, agent status, persistent sessions, and remote-machine workflow through a hands-on review. I also cover where plain tmux is enough—and when I’d choose a b…
My Daily Tech Stack: Apps and Tools I Actually Use
My daily tech stack is not just a list of apps. It is a connected workflow that helps me document my HomeLab, work from the terminal, use AI with real project context, test applications locally, and safely move more complex tasks onto real…
Terraform + Ansible: The DevOps Workflow That Actually Works
Terraform vs Ansible is often the wrong debate. In this video, I’ll explain Infrastructure as Code, compare how Terraform/OpenTofu and Ansible actually work, and use my Proxmox HomeLab as one consistent example. We’ll look at where their r…
My NEW AI Terminal and Code Editor // Orca Review
I tested Orca, a new Agent Development Environment that tries to combine AI terminal agents, code editing, Git worktrees, browser previews, mobile control, and multi-agent orchestration into one workflow. In this video, I’ll show how Orca…
Better HomeLab Secret Management // Infisical Tutorial
HomeLab secrets usually start simple: one .env file next to a Docker Compose stack. But over time, those secrets spread into GitLab variables, deployment scripts, copied folders, backups, notes, and places where they should not live. In th…