Connect Juno to Glean so people can search your learning content and build training from Glean Assistant.
This is Glean calling Juno — Glean acts as the MCP host and Juno is the server. It isn’t the Glean MCP server, which is the opposite direction (Glean’s own content exposed to assistants like Claude). Don’t set this up under Platform → Glean MCP servers.
Add Juno as a tool
A Glean administrator does this once for the organization.1
Open the Tools console
In Glean, open the Admin console and go to Platform → Tools.
2
Import an MCP server
Open the Vendor Provided Tools (via MCP) tab, select Add, then choose Import tools from MCP server. Juno isn’t a Glean certified built-in template, so import it rather than browsing the built-in servers.
3
Enter the Juno server details
Replace
<your-workspace> with your Juno subdomain. Juno’s authorization server supports OAuth 2.1 dynamic client registration, so there’s no OAuth client to create by hand and no client secret to enter.4
Connect and enable the tools
Select Connect to server and sign in to Juno. Glean uses this connection to discover Juno’s tools — it doesn’t sign in your users. Then use Edit settings to enable the Juno tools for Glean, and select Save.
Glean’s console labels change between releases. If what you see doesn’t match, follow Glean’s own guide for connecting remote MCP servers.
Use Juno in Glean
There’s no tool picker and nothing for a learner to turn on. They just ask Glean in their own words, naming the tool when it helps:“Use the Juno Journey tool to find our onboarding courses and summarize what we already have.”The first time someone uses a Juno tool, Glean pauses and shows a Connect prompt — they sign in to Juno once, and Glean remembers it. Their results are scoped to their own Juno role, so two people asking the same question may see different content.