Skip to main content
Add the Terminal49 MCP server as a tool in a Microsoft Copilot Studio agent so Copilot can answer questions with live container and shipment tracking data. Agents built in Copilot Studio can then be published to Microsoft 365 Copilot, Teams, and other channels.
No API key required. The Terminal49 MCP server supports OAuth 2.1 with Dynamic Client Registration, which maps to Copilot Studio’s OAuth 2.0 → Dynamic discovery authentication option. Users sign in with their Terminal49 credentials in the browser.

​
Prerequisites

  • Access to Microsoft Copilot Studio with permission to edit an agent and add tools.
  • The MCP tool configuration wizard enabled in your environment (Microsoft is rolling it out by region and tenant; if selecting the MCP option only opens documentation, the wizard isn’t enabled for your tenant yet).

​
Add the server to an agent

1

Open your agent's tools

In Copilot Studio, open your agent and go to the Tools page, then select + Add a tool.
2

Create the MCP tool

Select + New tool → Model Context Protocol, then enter:
3

Choose OAuth with dynamic discovery

Under Authentication, select OAuth 2.0 and choose Dynamic discovery. Copilot Studio discovers Terminal49’s authorization server and registers itself automatically — you don’t need to enter client credentials.
4

Connect and sign in

Create the tool, then select Connect (or open the connection manager) and sign in with your Terminal49 account in the browser window that opens.
5

Add the tool to the agent and test

Make sure the tool is enabled for the agent, then ask in the test pane:
“Using Terminal49, search for container CAIU1234567 and summarize its status.”

​
Test your connection

Ask the agent:
“List the tools available in the Terminal49 MCP server and what they’re for.”
It should list tools such as search_container, track_container, and get_container. See the tools reference for the full list, and Test Numbers for containers you can use during development.

​
Troubleshooting