Add Custom APIs and MCP Servers to Declarative Agents
Diesen Beitrag auf Deutsch lesen
A video tutorial shows how to connect Microsoft 365 Copilot declarative agents to custom HTTP APIs and MCP servers despite current Agent builder UI limits.
TL;DR
The tutorial shows how to create a declarative agent for Microsoft 365 Copilot, introduce a custom HTTP API, and test the agent calling backend logic. It also covers MCP servers, with PAYG and Copilot Credits possible, although Agent builder cannot add custom APIs or MCP servers directly.
Original by Giorgio Ughini, on Microsoft Copilot Studio CAT. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Build a plain declarative agent, connect the custom HTTP API or MCP server, and test the complete flow live before relying on it.
- Admins/CoE: Account for the current Agent builder limitation, because custom HTTP APIs and MCP servers cannot be added directly through its UI.
- Leadership/Business: Use the repeatable setup when agents need to reach backend logic, while recognising that the source presents this as a practical tutorial rather than theory.
Frequently asked questions
How can a Microsoft 365 Copilot declarative agent call a custom HTTP API?
Create the declarative agent, introduce the custom HTTP API, and test the complete flow so the agent calls the backend logic.
Can Agent builder directly add MCP servers to declarative agents?
No. The Agent builder UI cannot directly add MCP servers, so the tutorial shows an alternative wiring approach.
Does the declarative agent tutorial support PAYG with Copilot Credits?
Yes. The walkthrough says creating the plain declarative agent is possible with PAYG and Copilot Credits.