> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junojourney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Glean

> Add the Juno MCP server to Glean so Glean Assistant can work with your learning content.

export const RelatedPages = ({pages = []}) => {
  if (pages.length === 0) return null;
  return <>
      <br />
      <strong>Related articles</strong>
      <CardGroup cols={2}>
        {pages.map(page => <Card title={page.title} href={page.href} key={page.href} />)}
      </CardGroup>
    </>;
};

export const Prerequisites = ({items = []}) => {
  return <Note title="Before you start">
      {items.length > 0 && <ul>
          {items.map((item, index) => <li key={index}>{item}</li>)}
        </ul>}
    </Note>;
};

export const SupportContact = () => {
  return <Info title="Still need help?">
      Contact us at <a href="mailto:support@junojourney.com">support@junojourney.com</a> or use the support widget in Juno.
    </Info>;
};

<Info>
  Connect Juno to Glean so people can search your learning content and build training from Glean Assistant.
</Info>

<Note>
  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**.
</Note>

<Prerequisites
  items={[
"A Glean administrator with the Admin or Setup Admin role — there's no self-serve path for a learner",
"Your Juno workspace subdomain",
]}
/>

## Add Juno as a tool

A Glean administrator does this once for the organization.

<Steps>
  <Step title="Open the Tools console">
    In Glean, open the **Admin console** and go to **Platform → Tools**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Enter the Juno server details">
    | Glean field           | What to enter                                                  |
    | --------------------- | -------------------------------------------------------------- |
    | MCP server name       | `Juno Journey`                                                 |
    | Description           | Search and build learning content in Juno                      |
    | MCP server URL        | `https://mcp-prod.the-juno.com/mcp?workspace=<your-workspace>` |
    | Transport type        | **Streaming HTTP**                                             |
    | Authentication method | **Dynamic Client Registration**, or **OAuth User**             |

    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.
  </Step>

  <Step title="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**.
  </Step>
</Steps>

<Warning>
  Choose a per-user authentication method such as **OAuth User** or **Dynamic Client Registration**, so each person reaches Juno with their own account and their own permissions. **OAuth Admin**, **API Key**, and **OAuth Client Credentials** share one connection across everyone, which would give every Glean user the same Juno access.
</Warning>

<Note>
  Glean's console labels change between releases. If what you see doesn't match, follow Glean's own guide for connecting remote MCP servers.
</Note>

## 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.

## Using Juno in Glean Agents

Glean's support for remote MCP servers is generally available in Glean Assistant and in **beta** for Glean Agents. In Agent Builder, Juno's tools can be used in a **Plan and execute** step or an autonomous agent — they aren't available in single-step selections.

<SupportContact />

<RelatedPages
  pages={[
{ href: "/mcp/overview", title: "MCP overview" },
{ href: "/mcp/security", title: "Security & permissions" },
{ href: "/mcp/other-clients", title: "Other MCP clients" },
{ href: "/mcp/troubleshooting", title: "Troubleshooting" }
]}
/>