Copilot Studio MCP Servers: Choose the Right Build Path
Diesen Beitrag auf Deutsch lesen
Use a connector, Dataverse custom API or prebuilt MCP server before building custom infrastructure, then govern tools, identity and ownership.
TL;DR
Copilot Studio supports MCP through Streamable HTTP, with up to 128 tools per agent and 25 to 30 recommended. Use a connector, prebuilt server or Dataverse custom API first. Build a custom server when logic is complex, tools serve multiple clients, or MCP resources are required, while enforcing ownership and customer identity in server code.
Original by Zsolt Zombik, on Practical AI, Copilot & Modern Development Insights. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Prefer a connector when one agent needs a thin API wrapper or per-agent descriptions, because it avoids hosting.
- Admins/CoE: Apply Power Platform data policies because MCP access runs through connectors, and record who owns each server.
- Security/Compliance: Keep customer identity out of model-supplied tool arguments, validate ownership server-side, and require confirmation before write operations.
- Leadership/Business: Fund custom hosting only when shared tools, complex logic or resources justify it over simpler platform options.
Frequently asked questions
When should I build a custom MCP server for Copilot Studio instead of using a connector?
Build one when logic is complex, the same tools serve multiple clients, or MCP resources are needed. A connector suits a thin API wrapper or one agent.
How many MCP tools can a Copilot Studio agent use?
Copilot Studio supports up to 128 tools per agent, with 25 to 30 recommended. Each MCP server also counts against the agent tool total.
How does Copilot Studio apply DLP to MCP servers?
MCP access runs through Power Platform connectors, so data policies apply. An allowed MCP server exposes its full tool surface rather than individual actions.
