Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.

Microsoft Docs Research skill for the Microsoft technology ecosystem. Covers learn.microsoft.com and documentation that lives outside it (VS Code, GitHub, Aspire, Agent Framework repos). Default: Microsoft Learn MCP Use these tools for everything on learn.microsoft.com — Azure, .NET, M365, Power Platform, Agent Framework, Semantic Kernel, Windows, and more. This is the primary tool for the vast majority of Microsoft documentation queries. Tool Purpose microsoft docs search Search learn.microsoft.com — concepts, guides, tutorials, configuration microsoft code sample search Find working code snippets from Learn docs. Pass language ( python , csharp , etc.) for best results microsoft docs fetch Get full page content from a specific URL (when search excerpts aren't enough) Use microsoft docs fetch after search when you need complete tutorials, all config options, or when search excerpts are truncated. CLI Alternative If the Learn MCP server is not available, use the mslearn CLI from your terminal or shell (for example, Bash, PowerShell, or cmd) instead: MCP Tool CLI Command microsoft docs search(query: "...") mslearn search "..." microsoft code sample search(query: "...", language: "...") mslearn code search "..." language ... microsoft docs fetch(url: "...") mslearn fetch "..." Pass json to search or code search to get raw JSON output for further processing. Exceptions: When to Use Other Tools The following categories live outside learn.microsoft.com. Use the specified tool instead. .NET Aspire — Use Aspire MCP Server (preferred) or Context7 Aspire docs live on aspire.dev , not Learn. The best tool depends on your Aspire CLI version: CLI 13.2+ (recommended) — The Aspire MCP server includes built in docs search tools: MCP Tool Description list docs Lists all available documentation from aspire.dev search docs Weighted lexical search across aspire.dev content get doc Retrieves a specific document by slug These ship in Aspire CLI 13.2 ([PR 14028](https://github.com/dotnet/aspire/pull/14028)). To update: aspire update self channel daily . Ref: https://davidpine.dev/posts/aspire docs mcp tools/ CLI 13.1 — The MCP server provides integration lookup ( list integrations , get integration docs ) but not docs search. Fall back to Context7: Library ID Use for /microsoft/aspire.dev Primary — guides, integrations, CLI reference, deployment /dotnet/aspire Runtime source — API internals, implementation details /communitytoolkit/aspire Community integrations — Go, Java, Node.js, Ollama VS Code — Use Context7 VS Code docs live on code.visualstudio.com , not Learn. Library ID Use for /websites/code visualstudio User docs — settings, features, debugging, remote dev /websites/code visualstudio api Extension API — webviews, TreeViews, commands, contribution points GitHub — Use Context7 GitHub docs live on docs.github.com and cli.github.com . Library ID Use for /websites/github en Actions, API, repos, security, admin, Copilot /websites/cli github GitHub CLI ( gh ) commands and flags Agent Framework — Use Learn MCP + Context7 Agent Framework tutorials are on learn.microsoft.com (use microsoft docs search ), but the GitHub repo has API level detail that is often ahead of published docs — particularly DevUI REST API reference, CLI options, and .NET integration. Library ID Use for /websites/learn microsoft en us agent framework Tutorials — DevUI guides, tracing, workflow orchestration /microsoft/agent framework API detail — DevUI REST endpoints, CLI flags, auth, .NET AddDevUI / MapDevUI DevUI tip: Query the Learn website source for how to guides, then the repo source for API level specifics (endpoint schemas, proxy config, auth tokens). Context7 Setup For any Context7 query, resolve the library ID first (one time per session): 1. Call mcp context7 resolve library id with the technology name 2. Call mcp context7 query docs with the returned library ID and a specific query Writing Effective Queries Be specific — include version, intent, and language: Include context: Version when relevant ( .NET 8 , Aspire 13 , VS Code 1.96 ) Task intent ( quickstart , tutorial , overview , limits , API reference ) Language for polyglot docs ( Python , TypeScript , C )

microsoft-docs