Skip to main content

​
Overview

Glean is an enterprise AI platform whose chat and agents work over a company’s own knowledge. It connects to remote MCP servers as vendor provided tools, added once by an admin from the Admin console. StackOne connects to Glean with OAuth, so each user authorizes their own toolset and only reaches the linked accounts they have access to.
Adding an MCP server takes a Glean Admin or Setup Admin role, and agent support is in beta. Requirements and the menu labels change often, so see Glean’s Connect remote MCP servers guide for the current flow.

​
Prerequisites

  • A StackOne project you are a member of.
  • A connector profile in the project for each provider the client should reach, with the actions you want exposed enabled.
  • (Optional) A linked account for each provider. Accounts can also be linked during the consent flow.

​
Setup

1

Open the Tools page

  1. Open the Glean Admin console.
  2. On the Tools page, click Add in the top right.
Glean Admin console Tools page on the Vendor Provided Tools via MCP tab, with an Add button in the top right
2

Import tools from an MCP server

  1. In the Add tools dialog, open the Vendor provided tools (via MCP) tab.
  2. Click Import tools from MCP server.
Glean Add tools dialog with the Vendor provided tools via MCP tab selected and the Import tools from MCP server option at the top
3

Configure the server

On the Configuration tab, fill in:
  • MCP server name (e.g. StackOne).
  • Description (e.g. MCPs powered by StackOne).
  • MCP server URL:
  • Transport type: Streaming HTTP.
  • Authentication Method: Dynamic Client Registration.
Glean MCP server configuration form with the name StackOne, a description, and the StackOne MCP server URL filled in
4

Approve the consent screen

Click Initiate connection. Glean opens StackOne in your browser.Sign in, pick the project and the linked accounts the connector should reach, then Authorize.
Connect to server now shows Connected, and the discovered tools appear on the Tools tab.
Your connection covers tool discovery and configuration only. Glean’s documentation is explicit that it “does not authorize end users”. Each teammate runs this same consent flow with their own StackOne login the first time they use a tool, so they only reach the accounts they have access to.
5

Set tool visibility

  1. On the Configuration tab, under Enable Tools click Edit Settings.
  2. Expand the surface you want the tools on: Chat, Agents, or Glean MCP Server.
  3. For each tool in that surface, set:
    • Access, the teammates who can use it. Copy to all tools applies one choice to the rest.
    • Run without user confirmation, whether it runs without asking first.
  4. Repeat for every surface the tools belong on, then click Save.
Glean Enable tools screen with the Agents section expanded, showing the Stackone Search Actions, Execute Action, Execute S1query Action, and List Accounts tools with access set to all teammates and run without user confirmation set to yes
A tool must be assigned to at least one teammate or team, or Glean disables it everywhere. Run without user confirmation applies to Agents only. See Glean’s tool visibility and run without user confirmation guides.
6

Verify

The server appears under Vendor Provided Tools (via MCP) with status Enabled.Try a prompt in Glean Chat (if you enabled the tools for Chat):
Every grant belongs to the teammate who approved it, so changing which accounts or actions Glean can reach means that person running the consent flow again. To revoke one, use Connected Apps in the StackOne dashboard.

​
Adding tools to a Glean agent

1

Create the agent

In Glean, go to the Agents tab and create an agent.
2

Add the StackOne MCP server as a tool

In the panel on the right, open Tools, click +, choose MCP, and select the StackOne server you added.
Glean agent builder with the Tools panel highlighted on the right and an Add tool button
3

Verify

Click Preview and ask the agent:
Then Publish to make it available to the teammates you granted access to.
All of the server’s tools are enabled on the agent automatically. Through the two Advanced Tool Search tools, Search and Execute, the agent can find and run the actions each teammate granted, against the linked accounts that teammate has access to.
Glean supports MCP tools in Plan and execute steps and autonomous agents, not in single-step selections. They are also unavailable in Fast mode.
A session token URL carries its own credential, so it covers the cases OAuth can’t: a shared server, a scheduled job, or anywhere nobody is present to approve a consent screen. For a comparison of each connection method, see Choosing a connection method.From the StackOne dashboard, go to Connectors, open a connector, then click Use in Agent.
  1. Pick a linked account.
  2. Set the expiry (one year by default).
  3. Select HTTPS MCP and copy the URL. It should be in the format of:
This URL covers one linked account, and anyone holding it has that access until it expires, so treat it like a password.To enable Advanced Tool Search, add the tool-mode query parameter to the URL:
Follow the Setup steps, with two fields changed:
  1. MCP server URL: Use the token URL.
  2. Authentication Method: None.

​
Optimize and secure

With your agent connected, use StackOne’s platform features to optimize performance and secure every call.

Advanced Tool Search

Reduce context and save tokens.

Deep Query

Search synced records for a fraction of the tokens.

Defender

Block prompt injections before they reach your agent.