CI HUB BRIGHT - CI HUB AI Connector for Copilot Studio

This guide walks you through building a CI HUB AI Connector in Microsoft Copilot Studio, from registering the CI HUB AI Connector server to publishing your finished agent. 

Once set up, the CI HUB AI Connector lets your agent search, retrieve, upload, rename, and manage digital assets across all DAM, PIM, MAM and cloud storage systems connected to your CI HUB account. Users can then do all of this in plain language, right from Teams or a SharePoint page, without opening CI HUB directly.

Who this is for: Administrators with access to Microsoft Copilot Studio, an active Microsoft 365 tenant, and a CI HUB account with MCP enabled. End-user setup is covered in a separate guide.

Before you start

Make sure you have the following ready:

• Copilot Studio access: Admin or Maker role on copilotstudio.microsoft.com
• Microsoft 365 tenant: Teams and SharePoint Online active
• CI HUB account: MCP feature enabled (contact CI HUB support if you're not sure)
• CI HUB AI Connector URL: https://mcp.ci-hub.com/mcp
• OAuth 2.0 support: The CI HUB AI Connector supports Dynamic Client Registration (DCR)

Step 1: Create a new agent in Copilot Studio

All configuration happens at copilotstudio.microsoft.com. Sign in with your Microsoft 365 admin account before you begin.

Create the agent

1. Go to copilotstudio.microsoft.com and sign in.
2. In the left sidebar, click Agents, then + New agent.
3. Give your agent a name (for example, "CIHUB AI Connector"), and optionally add a description. Click Create.
4. On the Overview tab, under Select your agent's model, choose your preferred model (for example, GPT-4o or GPT-5 Chat).

Configure the agent's instructions

On the Overview tab, find the Instructions field and enter a system prompt that tells the agent how to behave. Here's a recommended baseline for CI HUB:

You are the CI HUB assistant.

When users ask about:

• assets

• images

• files

• brand resources

• DAM content

• creative assets

ALWAYS use the available MCP tools to search and retrieve information before answering. Never answer from general knowledge if a CI HUB tool can provide the information. Use the MCP tools proactively.

Tip: Expand these instructions to reflect your organization's asset taxonomy, provider names, or any domain-specific terms your users are likely to use.

Click Save when done.

Step 2: Register the CI HUB AI Connector

Next, register the CI HUB AI Connector as a tool for your agent. You only need to do this once per tenant, other agents can reuse the same connector afterward.

Open the Tools tab

1. Inside your agent, click the Tools tab in the top navigation bar.
2. Click + Add a tool. The Add tool panel opens, showing available connectors, flows, and protocols.

Add a Model Context Protocol tool

1. Under Create new, click the Model Context Protocol tile.
2. Fill in the form with these values:
   • Server name: CI HUB AI Connector
   • Server description: CI HUB AI Connector lets AI tools access and use your digital assets securely. Connect your content systems and enable AI-powered workflows.
   • Server URL: https://mcp.ci-hub.com/mcp
   • Authentication: OAuth 2.0
   • OAuth Type: Dynamic discovery (recommended)

   Note: Dynamic discovery requires the CI HUB AI Connector to expose a valid registration_endpoint in its OpenID Connect configuration. This is supported by default on https://mcp.ci-hub.com/mcp.

3. Click Create. Copilot Studio registers the MCP server and creates a custom connector, you'll see a confirmation banner: "CI HUB AI custom connector has been created."
4. The connection status will show Not connected. Click the Connection dropdown, select + New connection, and follow the OAuth flow to authenticate with your CI HUB account. Once complete, the status turns green (Connected).
5. Click Add and configure. Copilot Studio discovers all available tools from the MCP server and lists them under the Tools tab.

Review and enable MCP tools

By default, tools may be toggled off. Enable the ones relevant to your use case:

• Search-Asset: Search assets across connected providers by keyword, folder, or filter
• Get-Asset-Download-URL: Generate a temporary 20-minute download URL for a specific asset
• Upload-Asset-By-URL: Upload an asset into a folder using a public URL
• Rename-Asset: Rename an existing asset by ID
• Delete-Asset: Permanently delete an asset, irreversible, use with caution

Recommended baseline: For a read-only agent (recommended for most users), enable only Search-Asset and Get-Asset-Download-URL. Restrict Delete-Asset to admin-level agents.

Toggle each tool on using the switch in the Tools table, then click Save.

Step 3: Test the agent

Before publishing, confirm the agent can successfully call CI HUB AI Connector tools.

1. Click the Test button (top right). A chat panel opens on the right side of the screen.
2. Try one of these test prompts:
   • "Show me the latest brand assets"
   • "Search for product images"
   • "Find files tagged with 'campaign 2026'"
3. In the Activity tab, confirm the agent invoked Search-Asset and received results from CI HUB. If no results appear, check the connection status in the Tools tab.

Before you troubleshoot further: In your agent's Settings, double-check that Use generative AI orchestration for your agent's responses? is set to Yes. If it's off, the agent won't reliably decide on its own when to call the CI HUB AI Connector tools. 

Common issue: If the agent responds with general knowledge instead of CI HUB results, revisit the Instructions field and make sure the "ALWAYS use MCP tools" directive is present and saved.