Microsoft 365 Agents Toolkit MCP Server

What it does

Microsoft's MCP server for people building agents and apps for Microsoft 365, Microsoft 365 Copilot and Teams. It lives in the Microsoft 365 Agents Toolkit repository and is meant to sit in an editor's chat agent (the docs walk through VS Code with GitHub Copilot) while you write app manifests and agent code.

Its most concrete tool, get_schema, downloads the official JSON schema for a Teams app manifest, a declarative agent manifest, an API plugin manifest or the m365agents.yaml project file from developer.microsoft.com, for a given version or the newest one it knows about. Schemas are cached in memory for the life of the process.

The other three tools, get_knowledge, get_code_snippets and troubleshoot, do not search anything themselves. In the source on the dev branch (src/retriever.ts) each returns the user's question followed by a fixed block of guidance: a list of Microsoft Learn links, and an instruction to use the Microsoft Learn MCP server (for docs, samples and code) or the GitHub MCP server (for issues in the Teams and Agents repositories). In practice they are useful only when one of those servers is also connected.

With get_schema set to "latest", the code currently maps to app manifest v1.25, declarative agent v1.6, API plugin v2.4 and m365agents.yaml v1.11 (src/fetcher.ts).

What it needs

Node.js 20 or newer (package.json engines) to run it with npx, and internet access to developer.microsoft.com for schema downloads. The docs set it up in VS Code (stable or Insiders) with the GitHub Copilot and GitHub Copilot Chat extensions in Agent mode; Visual Studio needs manual MCP configuration. No Microsoft 365 account or key is needed. For the docs and troubleshooting tools to lead anywhere, the Microsoft Learn MCP server or the GitHub MCP server should also be connected.

Limits

It does not create, build, provision or deploy projects; it only returns schemas and guidance text. get_knowledge, get_code_snippets and troubleshoot return the same static guidance for any question rather than search results (src/retriever.ts). get_schema covers only four schema types, and "latest" resolves to versions fixed in the code, so a newer published schema needs an explicit version. The npm latest tag points at a beta build (0.2.2-beta), and the README says the server is being built in the open; the code described here is from the dev branch.

Who it suits

It suits developers writing Teams app or Microsoft 365 Copilot agent manifests who want their assistant to check against the real schema version. It runs locally over stdio, reads public schemas only and changes nothing, with no sign-in. For documentation search, pick the Microsoft Learn MCP server (which we hold), which these tools send the assistant to anyway; for searching issues in the Microsoft repositories, the GitHub MCP server. Developers who want scaffolding or deployment from the terminal should use the Agents Toolkit CLI instead, which is not an MCP server.