5 posts · page 1/1
Most teams ship one of these and call the job done. MCP gives the agent tools. Skills tell it which to use, in what order, with which fallbacks. Without skills, your MCP integration ends with users asking 'okay, what now?'
Seven architectural layers sit between you and the model in Claude Code, and each one is load-bearing. Here's what every layer actually buys you when you're eight hours into a refactor — and what specifically breaks when a tool pretends it doesn't need one.
Microsoft shipped 8 Work IQ MCP servers for SharePoint, Teams, Outlook, and the rest of Microsoft 365 — plus the line that actually mattered: these servers are reachable from Claude, LangChain, and any MCP-compliant framework. That's Microsoft, the company that turned Graph connectors into a decade-long moat, endorsing Anthropic's open protocol as the common plane. Here's what that reframes about MCP, and which of the 8 servers are worth reaching for first.
Microsoft's Agent Framework 1.0 merges Semantic Kernel and AutoGen into one production SDK for .NET and Python — with A2A and MCP interop, OpenTelemetry baked in, and an LTS commitment. The "which agent framework do we standardize on?" meeting just got shorter.
Ten repos that genuinely change how I work with Claude Code — and a suggested order for adopting them. Install one, use it for a week, keep only the ones that stuck. Never install a bundle.