Post

Connect MCP Servers To Declarative Agents With M365 Agents Toolkit

Diesen Beitrag auf Deutsch lesen

Matthew Devaney walks through connecting three MCP servers to declarative agents: Microsoft Learn with no authentication, Atlassian with dynamic OAuth and GitHub with static OAuth registration.

TL;DR

Declarative agents built with M365 Agents Toolkit can call MCP servers to reach external systems. Microsoft Learn's MCP server needs no authentication; Atlassian's uses OAuth with dynamic registration and prompts the user to sign in; GitHub's requires a registered OAuth app with client ID, secret and scopes such as repo and read:org. Each agent is provisioned from VS Code and tested in M365 Copilot.

Original by Matthew Devaney, on Matthew Devaney. Read the original

This is our own summary, not a republication or full translation.

Governance takeaway

  • Makers: Match the MCP server authentication type to the target service when building a declarative agent: none for Microsoft Learn, dynamic OAuth for Atlassian, static OAuth with client ID, secret and scopes for GitHub.
  • Admins/CoE: Track which MCP endpoints and permission scopes makers are wiring into agents, since provisioned agents can read and write external systems like JIRA and GitHub.
  • Security/Compliance: OAuth scopes such as repo and read:org define what an agent may access, so review each OAuth app registration and keep client secrets controlled.

Frequently asked questions

Which MCP servers can a declarative agent use without any authentication?

The Microsoft Learn MCP server works with no authentication. Its endpoint at learn.microsoft.com/api/mcp gives agents access to trusted Microsoft documentation and code samples.

What is the difference between dynamic and static OAuth registration for MCP servers?

With dynamic registration, Atlassian handles the OAuth setup during sign-in. With static registration, as for GitHub, you register an OAuth app yourself and supply client ID, secret and scopes.

Which OAuth scopes do I need for the GitHub MCP server?

The walkthrough uses the scopes repo, read:org and read:user. They tell the GitHub MCP server what access the OAuth app has, such as reading repositories.

Summary by KMUpower, licensed under CC BY 4.0 . Rights to the original article remain with its author.

Privacy Policy · Legal notice

Microsoft and the Power Platform product names (for example Power Apps, Power Automate, Copilot Studio) are trademarks of the Microsoft group of companies. This is an independent website. It is not operated, sponsored or endorsed by Microsoft.