Microsoft Docs
The Microsoft Docs MCP Server connects AI assistants directly to Microsoft’s official documentation through the Model Context Protocol.
When you ask a question, the MCP can ground its answer in the latest, most accurate information straight from the source.
Features
- 🔍 Semantic Search: Advanced vector search finds contextually relevant documentation across all Microsoft sources
- 📚 Comprehensive Coverage: Access Microsoft Learn, Azure documentation, Microsoft 365 docs, and other official sources
- ⚡ Real-time Updates: Always current with the latest published Microsoft documentation
- 🎯 Optimized Content Delivery: Returns up to 10 high-quality content chunks (max 500 tokens each) with article titles and URLs
- 🔌 Universal Compatibility: Works with any IDE or tool supporting the Model Context Protocol
- ☁️ Cloud-hosted: No local installation required – connects via remote HTTP endpoint
- 🤖 AI-optimized: Content chunking designed specifically for AI assistant consumption
Use Cases
- Azure Development Workflows: Quickly reference Azure CLI commands, ARM template syntax, and service configurations while writing infrastructure code without opening multiple browser tabs
- Microsoft 365 Integration Projects: Access Graph API documentation, SharePoint development guides, and Teams app development resources directly within your coding environment
- Troubleshooting Complex Microsoft Technologies: Get instant access to official troubleshooting guides and best practices when debugging issues with Microsoft services or tools
How to Use It
The Microsoft Docs MCP Server operates as a remote endpoint, so no local installation is required. You simply configure your MCP-compatible client to connect to the service.
Server Endpoint:
https://learn.microsoft.com/api/mcpBasic Configuration (JSON):
{
"microsoft.docs.mcp": {
"type": "http",
"url": "https://learn.microsoft.com/api/mcp"
}
}IDE-Specific Installation
VS Code & VS Code Insiders:
- Click the one-click install button in the official repository
- The extension automatically configures the MCP connection
- Restart VS Code to activate the server
Cursor:
- Use the provided Cursor install button for automatic setup
- The server appears in your available MCP tools list
- No additional configuration needed
Visual Studio:
- Manually add the configuration to your MCP settings
- Use
"type": "http"in your configuration - Restart Visual Studio to recognize the new server
Roo Code:
- Add the server configuration manually
- Use
"type": "streamable-http"for Roo Code compatibility - Save and restart the application
Using the MCP Server
- Activate Agent Mode: In VS Code, open GitHub Copilot and switch to Agent mode
- Verify Connection: Check that “Docs MCP Server” appears in your tools list
- Query Documentation: Use prompts like “What are the az cli commands to create an Azure container app according to official Microsoft Learn documentation?”
- Review Results: The assistant retrieves and references official Microsoft documentation in its responses
FAQs
Q: Why do I get a “405 Method Not Allowed” error when I paste the URL into my browser?
A: The URL is an API endpoint designed for programs like your IDE’s AI assistant to communicate with, not for direct browser access. This error is expected and means the endpoint is working correctly, just not for web browsers.
Q: The tool isn’t appearing in GitHub Copilot. What should I do?
A: First, restart VS Code. That often resolves discovery issues. Also, confirm you are in “Agent” mode in the Copilot Chat window, as tools are only available in this mode. Finally, double-check your MCP JSON configuration for any typos.
Q: What specific tool does this server provide?
A: It provides one main tool: microsoft_docs_search. This tool takes a single string parameter called query to perform a semantic search against the documentation.
Latest MCP Servers
CVE
WebMCP
webmcp is an MCP server that connects MCP clients to web search, page fetching, and local LLM-based extraction. It’s ideal…
Google Meta Ads GA4
Featured MCP Servers
Notion
Claude Peers
Excalidraw
FAQs
Q: What exactly is the Model Context Protocol (MCP)?
A: MCP is an open standard, like a common language, that lets AI applications (clients) and external data sources or tools (servers) talk to each other. It helps AI models get the context (data, instructions, tools) they need from outside systems to give more accurate and relevant responses. Think of it as a universal adapter for AI connections.
Q: How is MCP different from OpenAI's function calling or plugins?
A: While OpenAI's tools allow models to use specific external functions, MCP is a broader, open standard. It covers not just tool use, but also providing structured data (Resources) and instruction templates (Prompts) as context. Being an open standard means it's not tied to one company's models or platform. OpenAI has even started adopting MCP in its Agents SDK.
Q: Can I use MCP with frameworks like LangChain?
A: Yes, MCP is designed to complement frameworks like LangChain or LlamaIndex. Instead of relying solely on custom connectors within these frameworks, you can use MCP as a standardized bridge to connect to various tools and data sources. There's potential for interoperability, like converting MCP tools into LangChain tools.
Q: Why was MCP created? What problem does it solve?
A: It was created because large language models often lack real-time information and connecting them to external data/tools required custom, complex integrations for each pair. MCP solves this by providing a standard way to connect, reducing development time, complexity, and cost, and enabling better interoperability between different AI models and tools.
Q: Is MCP secure? What are the main risks?
A: Security is a major consideration. While MCP includes principles like user consent and control, risks exist. These include potential server compromises leading to token theft, indirect prompt injection attacks, excessive permissions, context data leakage, session hijacking, and vulnerabilities in server implementations. Implementing robust security measures like OAuth 2.1, TLS, strict permissions, and monitoring is crucial.
Q: Who is behind MCP?
A: MCP was initially developed and open-sourced by Anthropic. However, it's an open standard with active contributions from the community, including companies like Microsoft and VMware Tanzu who maintain official SDKs.



