Connect Kaiterra MCP to Microsoft Copilot (Beta)
Beta feature. Kaiterra MCP is in beta. Tools and capabilities may change at any time.
This guide is for administrators. You configure the Kaiterra MCP server once in Microsoft Copilot Studio, then publish it so your team can ask about building air quality from Microsoft 365 Copilot.
For other assistants, see Connect your AI assistant to Kaiterra with MCP.
Before you start
Check your Kaiterra sign-in method
Users authenticate to their Kaiterra account when they connect the agent. In enterprise Copilot deployments this is usually your corporate identity provider via SAML SSO, such as Microsoft Entra. Kaiterra supports SAML 2.0. See the SSO setup guide.
Confirm before rolling this out:
- Your subscription has SAML SSO enabled, and an admin has configured it under Manage → Organization → SSO. You'll need your IdP's URL, Issuer, and X.509 certificate.
- Each user has an active account with your identity provider.
If your organization has enabled Login with SSO only, everyone connecting the agent must sign in through your IdP. This blocks third-party contractors without an organizational email address. Plan connections accordingly, or use non-enforced SSO if external users need access.
What you'll need
- A Microsoft Copilot Studio license to build the agent, and a Microsoft 365 Copilot license for each end user.
- The Kaiterra MCP server URL:
https://app.kaiterra.com/ai/mcp
Step 1: Create the agent
- Sign in to Microsoft Copilot Studio.
- In the left pane, select Create → New agent.
- Give it a name, such as Kaiterra IEQ Monitoring, and a short description.
Step 2: Add the MCP tool
- Open the agent and select Tools → Add a tool.
- Search for Model Context Protocol, select it, then choose New tool → Model Context Protocol.
- Enter the server details:
- Server Name:
Kaiterra MCP - Server Description:
Indoor environmental quality intelligence for commercial buildings - Server URL:
https://app.kaiterra.com/ai/mcp
- Server Name:
Step 3: Configure OAuth 2.0
Under Authentication, choose OAuth 2.0. Then use the Dynamic discovery path below. If your organization requires a pre-registered confidential client, use the Manual fallback instead.
Dynamic discovery (recommended)
- Set the type to Dynamic discovery.
- Select Create. Copilot Studio reads the server's discovery metadata, finds the authorization and token endpoints, and registers itself with Kaiterra. No Client ID, Client Secret, or URLs are required.
- Select Next, then continue to Step 4.
Manual fallback (only if your organization requires a pre-registered client)
- Set the type to Manual.
- Enter the five values your Kaiterra contact provided: Client ID, Client Secret, Authorization URL, Token URL Template, and Scopes.
- In Refresh URL, enter a single period:
. - Select Create.
- Copy the Redirect URL shown in the success message and send it to your Kaiterra contact to add to the OAuth app's allowed redirect URIs. If you own the app registration, add it yourself in the Microsoft Entra admin center.
- Select Next, then continue to Step 4.
Step 4: Create the connection
- Select the Connection dropdown, then Create new connection → Create.
- Sign in with your Kaiterra account in the window that appears, then select Add and configure.
- Confirm the server appears under Tools with its Kaiterra tools listed.
Step 5: Publish and share
- Select Publish.
- Use the ⋯ menu → Share to grant users the Viewer role.
- Under Channels, add Teams and Microsoft 365 Copilot.
For end users: first-time connection
- In Microsoft 365 Copilot, add the agent from the left pane.
- Ask a question, such as "How's the air quality in the Shanghai office?"
- When prompted, select Open Connection Manager → Connect, sign in with your Kaiterra account, select Submit, then Retry your question.
You only need to do this once.
Example prompts
- "Give me a health check for [building]."
- "What's the CO₂ trend on the 3rd floor this week?"
- "Which devices have weak signal or are offline?"
- "Is [building] WELL v2 compliant this quarter?"
- "Compare CO₂ before and after we changed the HVAC schedule on [date]."
Troubleshooting
| Problem | What to do |
|---|---|
| Sign-in fails during connection | Confirm the redirect URI from Step 4 was added to the OAuth app registration. |
| OAuth setup won't complete on Dynamic discovery | Switch to the Manual fallback in Step 3 and request the five OAuth values from your Kaiterra contact. Contact Kaiterra Support if the issue persists. |
| Agent responds but returns no data | Check that the user's Kaiterra account has access to the building in the Kaiterra Data Platform. |
| User sees the wrong organization's buildings | Each account accesses one Kaiterra organization at a time. The user must sign in with the account or alias tied to the organization they need. |
| SSO users can't sign in | Confirm SSO is configured and the user is provisioned with your identity provider. See the SSO guide. For IdP issues, contact your IT team. |
| Tools don't appear after configuration | Republish the agent, then have users remove and re-add it in Microsoft 365 Copilot. |
For Kaiterra account or connection issues, contact Kaiterra Support. For Copilot Studio or licensing issues, contact your Microsoft administrator.
Related articles