AI & integrations
Connect Microsoft 365 Copilot
Add Timeglass as a connector for everyone in your Microsoft 365 organization.
Add Timeglass as a connector in Microsoft 365 Copilot, so people in your organization can ask Copilot about their time, projects, clients, and meetings.
Copilot asks Timeglass live, signed in as the person asking, and each person only reaches what their Timeglass account can already see. Timeglass data isn’t indexed or synced into Microsoft 365. Copilot’s answers stay in that person’s Copilot chat history, like any other Copilot conversation. Setup takes about ten minutes in two places: the Teams Developer Portal for sign-in, then the Microsoft 365 admin center for the connector itself.
Register sign-in in the Teams Developer Portal
- Start a new OAuth connectionSign in to the Teams Developer Portal, go to Tools → OAuth Client Registration, and select New OAuth connection.
- Fill in the form
- Name:
Timeglass - Client ID: any name, such as
microsoft-copilot - Client secret: any value, such as
unused. Timeglass doesn’t check it, because PKCE protects sign-in. - Authorization endpoint:
https://app.timeglass.ai/api/mcp/oauth/authorize - Token endpoint and Refresh endpoint:
https://app.timeglass.ai/api/mcp/oauth/token - Scopes:
mcp:read mcp:write offline_access
- Name:
- Turn on PKCETurn on Proof Key for Code Exchange (PKCE). Timeglass refuses sign-in without it.
- Save and copy the registration IDSelect Save and copy the OAuth client registration ID. You need it in the admin center.
For read-only access, use the scopes mcp:read offline_access instead. Copilot then only gets the tools that read data. Keep offline_access either way: without it, Timeglass sign-ins expire after an hour and people have to reconnect.
Create the connector in the admin center
- Add a custom connectorIn the Microsoft 365 admin center, go to Copilot → Connectors and open the Gallery tab. Under Created by your org, select Add on Create a new connector, then select Add under Connect to MCP server.
- Describe TimeglassSet the display name to
Timeglassand the base URL tohttps://app.timeglass.ai/api/mcp. Copilot reads the description to decide when to ask Timeglass, so say what your team uses it for. For example: “Timeglass records where people’s work time goes, from screen activity and meetings. Use it for questions about time spent on projects, clients, and activities, timesheets, who worked on what, and meeting transcripts and action items.” - Connect sign-inChoose OAuth 2.0, paste the registration ID from the Teams Developer Portal, and select Save.
Roll it out
The connector appears under Your connections. To try it with a few people first, open it, select Staged rollout, and add those users or a group. When it works, select Deploy to all users. Changes can take up to 10 minutes to reach Copilot.
Each person connects once. In Copilot Chat, they open Settings → Sources, find Timeglass, and select Connect. They sign in to Timeglass and select Connect again to approve Microsoft Copilot. Copilot starts in their default workspace, and they can ask it to switch to another one.
If something doesn’t work
- Sign-in fails with “PKCE code_challenge required”: PKCE is off in the Teams Developer Portal registration. Turn it on.
- People have to reconnect every hour:
offline_accessis missing from the scopes. Add it, then have people reconnect once. - Copilot never makes changes: the scopes don’t include
mcp:write, or the person is a viewer in their Timeglass workspace. - Timeglass is missing from Sources: under Agents → Settings, check that Allow agents and plugins built by your organization is on and that User access includes the person. Then check the staged rollout list and that they have a Copilot license.
If your network only allows certain source addresses, add Microsoft 365 Copilot’s egress addresses.
Disconnect or turn it off
People can disconnect in Copilot under Settings → Sources. To turn it off for everyone, disable or delete the connector under Copilot → Connectors → Your connections.