Connecting systemHUB to Microsoft Copilot Studio (AI Gateway / MCP)
Learn how to connect your systemHUB account to a Microsoft Copilot Studio agent using the AI Gateway, so you can query your systems, policies, and training content directly from Copilot.
๐ค Connecting Via Copilot Studio
๐ Before You Begin
- You need AI Gateway access. If you don't see Settings โ AI Gateway, email support@systemology.com and we'll switch it on for your role (admin seats have it by default).
- You need access to Microsoft Copilot Studio with permission to create or edit an agent. The standard Microsoft 365 Copilot Chat can't add custom connections, so this needs Copilot Studio.
- Have your systemHUB login handy, you will approve the connection at the end.
- Treat the token you generate like a password. Do not share it.
- Use Claude? Click here for Claude connection instructions.
- Use ChatGPT? Click here for ChatGPT connection instructions.
๐งญ Step 1 โ Get your connection details from systemHUB
- Log in to systemHUB.
- Go to Settings -> AI Gateway.
- Copy the Connector URL exactly as shown (a wrong character here is the #1 cause of failures).
- Note your company alias, this is your account subdomain (the part before .systemhub.com). Example: if you log in at acme.systemhub.com, your alias is acme.
- Click Generate to create your token. Each person needs their own token before they can approve a connection. โ ๏ธ If you already have one, only click Update if you need to. It revokes your old token and disconnects any AI you connected with it, including Claude or ChatGPT.
๐ Step 2 โ Add systemHUB as a tool in Copilot Studio
- Open Copilot Studio and select the agent you want to connect (or create a new one).
- Go to the Tools page for your agent.
- Click Add a tool โ New tool โ Model Context Protocol. The MCP setup window will appear.
- Enter your systemHUB details from Step 1:
- Server name: systemHUB
- Server description: Reads and manages our company's systems, policies and training content in systemHUB. (Copilot uses this description to decide when to use systemHUB, so keep it clear.)
- Server URL: paste the Connector URL from Step 1 (double-check it is exact).
- Under Authentication, select OAuth 2.0, then select Dynamic discovery as the type.
- Click Create, then click Next.
โ Step 3 โ Connect and approve
- In the Add tool window, select Create a new connection.
- A new window will now appear for you to sign into systemHUB
- When prompted, enter your company alias, this is your subdomain, all lowercase with no spaces (e.g. acme, not "Acme" or "My Company"), then click Continue
- Log in with your systemHUB credentials and click Approve Connection
- Back in Copilot Studio, click Add to agent. systemHUB will now appear in your agent's Tools list.
๐งช Step 4 โ Test the connection
- Open the Test panel for your agent in Copilot Studio.
- Then ask: "Can you check the folder tree and tell me what main root-level folders I have in my systemHUB account?" [SCREENSHOT PLACEHOLDER]
- If Copilot asks you to sign in or allow access, approve it. Copilot will then return your folders, which confirms it is working!
๐ ๏ธ Troubleshooting
- "Invalid or expired client ID"
- This is almost always the company alias or the token.
- Check the alias is your exact subdomain, lowercase, no spaces (acme, not "Acme" or your company name).
- Your token may have expired or been regenerated, so go back to Settings -> AI Gateway, generate a fresh token, and reconnect.
- Confirm the Connector URL was pasted exactly.
- No "AI Gateway" option under Settings
- Your role doesn't have AI access switched on yet. Only systemHUB support can enable it for Editor, Contributor and Reader roles, so email support@systemology.com and tell us which roles. Once it's on, each person's AI gets exactly their own seat's permissions: a Reader's AI can read but can't change anything.
- "No active agent token found" when approving
- You haven't generated your own token yet. Each person needs their own. Generate one in Settings โ AI Gateway, then approve again.
- Dynamic discovery fails or won't create the tool
- Go back to Authentication and select Manual instead. Paste your company alias in the Client ID field and your token in the Client secret field.
- systemHUB is added but Copilot never uses it
- Check the tool is switched on in your agent's Tools list, and that the server description clearly says what systemHUB is for.
- Can't add the tool, or it's blocked
- Your organisation's Microsoft data policies may block custom connections. Ask your Microsoft 365 or Power Platform admin to allow it.
- Connector adds but will not connect
- Remove it and re-add with a freshly generated token.
๐ You're All Set!
Your Copilot Studio agent can now read your systemHUB content. Try asking it to summarise a system, find a policy, or list what is in a folder.