MCP Server

The series so far has been about adding MCP servers to graphical AI surfaces — Claude Desktop, Raycast, VSCode's Copilot pane. Useful, but all of them are chat windows wearing different outfits. You type something, an AI types back, tools run in the middle. Terminal-based AI is a different interaction model. You're not in a chat — you're in a shell that also happens to have an agent in it. The agent reads files, runs commands, edits code, and uses MCP servers, but the shell i

The last three posts connected the same Intune MCP server to Claude Desktop, Raycast, and VSCode. The story there was simple: one trusted API, three interaction surfaces. Low security surface area — the MCP server calls Microsoft Graph on your behalf, and Microsoft Graph does what it's told. Filesystem MCP is a different animal. The server is trivially easy to set up. The tools it exposes are useful immediately. And the security model is meaningfully more complicated, becaus

Two posts ago we set up an Intune MCP server on macOS and wired it into Claude Desktop. Last time we added Raycast so the same server was reachable from a keyboard shortcut. This post closes the loop: connecting that same server to VSCode, so fleet context is available in the Copilot Chat pane while you're writing the PowerShell, Python, or Bash script that acts on it. This is the one I reach for most when the answer isn't "tell me a number" but "help me write something that

If you manage a Mac fleet through Microsoft Intune, you already know the rhythm: open the admin center, wait for it to load, click through three blades, copy a device ID, paste it somewhere, cross-reference with a report, and eventually answer a question that took your colleague ten seconds to ask in Slack. The Model Context Protocol (MCP) changes that workflow. By running an Intune MCP server locally on your Mac and connecting it to Claude, you can ask things like "how many