Connect Microsoft Copilot Studio to StackJack

Microsoft Copilot Studio adds MCP servers as agent tools (MCP is the Model Context Protocol, the open standard AI tools use to call external tools). The simplest path is OAuth 2.0 Dynamic discovery — Copilot Studio registers itself with StackJack automatically and you just sign in.

Prerequisites

• A Copilot Studio environment and an agent with generative (dynamic) orchestration turned on — MCP tools require it.
• A StackJack account that is a member of your workspace. Any team member can connect via Dynamic discovery — no admin-created credentials needed.
• Your StackJack MCP endpoint URL: https://mcp.stackjack.io/mcp.

Copilot Studio speaks MCP over Streamable HTTP only (it dropped the older SSE transport in August 2025) — StackJack uses Streamable HTTP, so no transport configuration is needed.

Connect with Dynamic discovery (recommended)

1. Go to copilotstudio.microsoft.com → Agents → create or edit an agent. Confirm generative (dynamic) orchestration is on for the agent.

2. Go to Tools → Add a tool → New tool → Model Context Protocol.

3. Fill in the wizard:

   Field	Value
   Server name	StackJack
   Description	Required — the model uses it to decide when to call StackJack, so describe what your connectors do (for example "MSP PSA and RMM tools: tickets, assets, patching")
   Server URL	https://compact.stackjack.io/mcp — the compact endpoint, recommended because Copilot Studio caps each server at 70 tools (requires catalog modes enabled for your org — see the note below and Tool limits). For the full catalog use https://mcp.stackjack.io/mcp.
   Authentication	OAuth 2.0 → Dynamic discovery

4. Click Create → Next → Create a new connection and sign in with your StackJack account (same email, password, and MFA as the portal) → Add to agent. Tools import automatically.

Large catalog? Copilot Studio caps each MCP server at 70 tools, so the wizard above points the Server URL at StackJack's compact endpoint https://compact.stackjack.io/mcp — Copilot Studio then receives a small, searchable tool list automatically. This works only after an admin enables catalog modes for your organization on Endpoints; until then the host serves the full catalog and you'll hit the 70-tool cap. See Tool limits.

Manual OAuth (fallback)

Copilot Studio offers three OAuth 2.0 modes: Dynamic discovery, Dynamic, and Manual. If you prefer static credentials, choose Manual, have an owner, co-owner, or Administrator create an MCP client in the portal (see Managing MCP credentials), and fill:

Tool limits

Microsoft Copilot Studio counts a maximum of 70 tools per MCP server — a limit we verified in practice; Microsoft's published quotas don't document a per-server MCP tool cap. (This is a different limit from GitHub Copilot in VS Code, which allows 128 tools per request — both numbers apply to different Copilot products.) StackJack can expose hundreds of tools depending on your connectors and plan, so you will exceed 70 quickly.

Keeping the served catalog small matters beyond the 70-tool count: Copilot Studio's generative orchestration also works within an overall per-agent tool budget (Microsoft documents roughly 128 tools per agent, across every tool the agent has — a different denominator from the 70-per-server cap above) and limits how large a single connector-action response may be, so a full multi-thousand-tool catalog can fail to load regardless. The options below keep StackJack's served list small enough to stay clear of all of these, best first:

• Connect to the compact endpoint (recommended). Set the wizard's Server URL to https://compact.stackjack.io/mcp instead of https://mcp.stackjack.io/mcp. Requests arriving on that host are served a compact catalog automatically — a small set of tools where the agent searches for and runs the rest on demand, with every tool still reachable and every permission still enforced. Copilot Studio can't carry a ?tools= query string on a server URL, so this dedicated host is how it selects the compact profile; nothing else in the setup changes. Prerequisite: an admin must first enable catalog modes for your organization on Endpoints — until then the host serves the full catalog and you'll hit the 70-tool cap.
• Set your connection to compact catalog mode (works today). On the Connectors page, in the My AI tool catalog card of your personal sign-ins section, set the catalog mode to Compact — your organization must first enable catalog modes on Endpoints. This serves your Copilot Studio connection the same small, searchable catalog with no special URL. See Choosing tools for each client and managing harness tool limits.
• Split into focused servers. Because the 70-tool budget is counted per MCP server, connect with an MCP client whose tool selection is trimmed to one job (for example a "Copilot – Tickets" client and a "Copilot – Devices" client) and add each to Copilot Studio as its own MCP server.

Troubleshooting

• The MCP option doesn't appear when adding a tool — the agent's generative orchestration is off; turn it on first.
• Sign-in says no account was found — sign up in the portal first, or ask your team admin for an invite.
• For anything else, see Connection troubleshooting.