MCP

Connect Microsoft Copilot to CastHub

Setup steps for Copilot Studio and GitHub Copilot in VS Code, what Copilot can do in CastHub, how permissions work, and the known limits.

Connect Microsoft Copilot to CastHub to manage your digital signage account in natural language. This guide covers Microsoft 365 Copilot through Copilot Studio agents and GitHub Copilot in Visual Studio Code.

Prerequisites

An active CastHub account. The connector does not create accounts. Sign up first at https://dashboard.cast-hub.com/register-user.

The connector works with any CastHub plan, including the 14-day free trial. Feature access matches your existing account.

You can sign in with your CastHub email and password, Google, or Microsoft.

Connect through Copilot Studio

For Microsoft 365 Copilot users, custom MCP servers are added through Copilot Studio agents.

  1. Open Copilot Studio and select or create the agent you want to extend.
  2. Under Tools, add a custom MCP server.
  3. Set the server URL to https://webapi.cast-hub.com/mcp.
  4. Configure OAuth using the discovery metadata at https://webapi.cast-hub.com/.well-known/oauth-authorization-server.
  5. Publish the agent.
  6. Sign in to CastHub when prompted on first use.

Connect through GitHub Copilot in VS Code

For developers using GitHub Copilot Chat in VS Code, add CastHub as an MCP server in your mcp.json configuration.

Add the following to your workspace or user mcp.json:

{
  "servers": {
    "casthub": {
      "url": "https://webapi.cast-hub.com/mcp"
    }
  }
}

VS Code will prompt for OAuth sign-in on first tool use. Sign in with your CastHub credentials, or with Google or Microsoft.

No API key is required for either path. Authentication uses OAuth 2.0 with PKCE and dynamic client registration.

What you can do

Presentations

Example prompts:

“List my presentations.”

“Create a presentation called Lobby Loop with a welcome web page and our promo image.”

“Delete presentation 42.”

Preview

After creating a presentation, Copilot returns a preview URL you can open in a browser to see it on a temporary preview device.

Devices and groups

Example prompts:

“Show all my devices.”

“Move device 12 to the Lobby group.”

“Create a device group called Cafeteria.”

Scheduling

Example prompts:

“Assign the weekday schedule to the Lobby group.”

“Show my weekly schedule.”

Alerts

Example prompts:

“Start a text alert on all groups: Building closing in 15 minutes.”

“Stop all alerts.”

Device commands

Example prompts:

“Reboot the Entrance display.”

“Turn the Lobby screen off.”

Disruptive commands prompt for confirmation before running.

Permissions and safety

Read-only tools that list or view data run freely. Write actions such as create and update are marked explicitly. Destructive actions such as delete, alerts, and reboots are marked so Copilot requests your confirmation before running them.

Capabilities summary

PropertyValue
Connector typeRemote (Streamable HTTP)
AuthenticationOAuth 2.0 with PKCE and dynamic client registration
AccessRead and write
ToolsApproximately 45 across presentations, slide media, devices, device groups, schedules, alerts, device commands, and dashboard

Limitations and troubleshooting

Copilot Studio requires a Microsoft 365 plan that includes Copilot or Copilot Studio licensing.

GitHub Copilot MCP support requires a recent version of VS Code and an active GitHub Copilot subscription.

The connector requires a CastHub account. It cannot register new users.

If the connection fails or tools do not appear, remove and re-add the server, then sign in again.

Support

support@cast-hub.com

Scroll to Top