Why I Switched to Context Forge for Azure MCP: Better Auth & Registry скачать в хорошем качестве

Why I Switched to Context Forge for Azure MCP: Better Auth & Registry

In today's video, we are diving deep back into the homelab to solve some common frustrations with the Model Context Protocol (MCP). While MCPO is a great starting point, I’ve run into limitations—specifically around passing authentication from Open WebUI. I’ll show you why I’m transitioning to Context Forge to act as my MCP registry and gateway. We’ll walk through: The Problem: Why the official Microsoft Azure MCP server broke and the auth limitations of current setups. The Setup: How to register MCP servers manually in Context Forge using Streamable HTTP or SSE. Virtual Servers: Scoping permissions and tools to specific teams or private projects. Live Demo: Watching a 120B model interact with live Azure resources (Resource Groups, Public IPs) through Open WebUI. I am also working on a custom Azure MCP server written in Go to provide a more stable, high-performance alternative to the current options. If there is enough interest, I’ll be looking into open-sourcing that code soon! https://github.com/IBM/mcp-context-forge https://github.com/open-webui/mcpo Timestamps: 0:00 Intro: The State of MCP in the Homelab 0:45 Why MCPO isn’t enough for advanced Auth 1:30 Walking through the Context Forge Registry 2:15 Configuring SSE vs. Streamable HTTP 3:00 Virtual Servers & Tool Scoping 4:10 Live Demo: Managing Azure via Open WebUI 5:00 Future Plans: Custom Go-based Azure MCP Server Connect: GitHub: https://github.com/Quazmoz Website: https://profile.quinnfavo.com #MCP #ContextForge #Azure #DevOps #Homelab #AI #OpenWebUI #Automation #CloudComputing #ModelContextProtocol #SelfHosted #SysAdmin