Glean: connect your team's Glean

Member·4 minutes to read

What this page is for

Glean runs one MCP server for each company that uses it. The Glean tile in the catalogue connects a bot to your team's server: you paste its URL, sign in to Glean in your browser, and approve the tools Glean lists. Then a bot can search your company's Glean, ask Glean's assistant and read documents Glean finds, as you, seeing only what you can see in Glean.

Before you start

A Glean account at your company, one you can sign in to in a browser.
Your team's Glean MCP server URL. It looks like https://your-company-be.glean.com/mcp/default. Ask your Glean admin for it, or copy it from Glean's MCP configurator. The end may be a name other than default if your admin created more than one server.
Glean's MCP servers switched on. Glean switches them on by default; a Glean admin can switch them off under Platform → Glean MCP servers.
Nothing to install and no key to copy. Any member can do this, with or without an organisation.

Steps

Open Plugins from the sidebar and find the Glean card.
Press Add server… on the card. The Add Glean form asks for Your own address: paste the URL whole, as Glean shows it. Press Continue.
Glean asks you to sign in, so Botseon shows Sign in to this server. Press Connect. Glean's sign-in page opens in a new tab: sign in with your company account and allow access. The tab closes or says you can go back.
Botseon lists the tools your Glean server offers, with Glean's own descriptions (if you left the page, press Review tools on the server's row). Press Install to approve them.
Give the server to a bot from the bot's settings.

A worked example

You ask: "What did we decide about the Q3 launch date? Check Glean."

The bot calls Glean's search tool. An approval card names the tool and the query; you approve.
Glean answers with the documents and messages that match, from the sources your company connected to Glean.
If the bot wants a whole document, it calls the read-document tool, after another approval card.

What can go wrong

"… is not an address of the shape this server has." The URL is not a Glean MCP server URL. Check that the host ends in -be.glean.com (not your Glean web address without -be), that the path is /mcp/<server name>, and that nothing follows it: no /sse, no ?….
"This server only accepts apps its supplier has registered by hand." Your Glean tenant does not let new apps register themselves. A Glean admin creates an OAuth client in Glean with the redirect address shown on Botseon's Registered apps for MCP servers page; a Botseon organisation admin enters it there as A server members add by address, named Glean, with your team's URL. You then add the server with Add an MCP server under the name Glean and that URL, and sign in as above.
Access was not allowed. You pressed cancel on Glean's page, or Glean refused you. Press Connect again.
A tool fails after a while. Your Glean sign-in expired or was revoked. Press Reconnect.

Limits

A bot sees only what you can see in Glean, through the tools your Glean server offers. Botseon adds no Glean tools of its own.
Every Glean tool asks you before it runs.
If your Glean admin changes the server's tools, Botseon asks you to approve the new list before the bot uses it.

Disconnecting

In Botseon: on the server's row, Sign out forgets your Glean sign-in; Remove removes the server and every bot's access to it.
At Glean: your Glean admin can revoke the app's access in Glean's admin console (Settings → Third-party access (OAuth)).