Skip to main content
An IT admin adds StackOne to the Glean organization, bringing Linked Accounts from many providers. Each user then connects with their own accounts: an HR manager uses Glean Assistant with Workday, Greenhouse and BambooHR, and a support lead builds in Glean Agents with Zendesk, Salesforce and Slack.
Make StackOne available to everyone in your Glean organization as a vendor provided tool. Each person then signs in with their own StackOne login and reaches only the systems they’ve been given access to in StackOne.

Before you start

Adding an MCP server takes a Glean Admin or Setup Admin role, and agent support is in beta. You sign in to StackOne yourself during setup, so Glean can discover the tools. In StackOne:
  • 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.

Add StackOne to Glean

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 (for example, StackOne).
  • Description (for example, 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.
A token app URL carries its own credential, so it covers the cases OAuth can’t: a client without OAuth support, 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.Create a token app under Connected Apps → Token apps, select the Linked Accounts it covers, and copy its MCP URL:
One URL covers every account the token app includes, 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 steps above, with two fields changed:
  1. MCP server URL: Use the token URL.
  2. Authentication Method: None.

Roll it out

StackOne is now available for your users in Glean. Make sure the following is ready before rolling out:
  • Add users. Invite or provision users via SSO/SCIM. See Manage Team.
  • Create groups. Organize teams into groups to control which systems each team reaches.
  • Set up connectors. Define Connector Profiles to scope provider actions for specific functions.
  • Link accounts. Link shared company accounts, or let users link their own accounts. See Linking Accounts.
Then send users one of the following guides, depending on the product:

Glean Assistant

For people using StackOne in Glean Assistant.

Glean Agents

For people building agents in Glean’s Agent Builder.

Control what Glean can reach

Set tool visibility above decides which surfaces and teammates see each tool. Within StackOne, each teammate can only approve what their Connector Profiles and Linked Accounts already allow.