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

# Glean - Make StackOne Available

> Allow your users to connect to work systems with StackOne.

![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.](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/glean/admin-setup.svg?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=450f0f79543feff11eac2dd7f970334a)

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](https://docs.stackone.com/gateway/concepts/organizations-and-projects.md) you are a member of.
* A [connector profile](https://docs.stackone.com/connect/managing-connectors/connector-profiles.md) in the project for each provider the client should reach, with the actions you want exposed enabled.
* (Optional) A [linked account](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md) 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**](https://app.glean.com/admin/tools).
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](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/glean/glean-vendor-provided-tools.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=a8135ba5ce833474dcb1cc8234e3c3ee)

**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](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/glean/glean-add-tools-import-mcp.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=aa4e312551d395246155beb0f52399aa)

**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**:

  ```text theme={null}
  https://mcp.stackone.com/mcp
  ```

* **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](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/glean/glean-mcp-configuration.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=410387ea884329d5c1380fc5619c3fe9)

**4. Approve the consent screen**

Click **Initiate connection**. Glean opens StackOne in your browser.

Sign in, pick the project and the [linked accounts](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md) the connector should reach, then **Authorize**.

> [accordion] Walk through the consent screen
>
> 1. **Sign in to StackOne.** If you are already signed in to the dashboard you skip straight to the next step.
> 2. **Check where the connection returns.** The line under the client's logo shows where it goes after you approve. If it names localhost or an app on this device, only continue if you started the connection from that client.
> 3. **Select a project.** Select the project you would like to associate the connection with. If you belong to one project, this step is skipped.
> 4. **Select accounts and actions.** Existing linked accounts are shown. New accounts can be linked by clicking **+ Link Account**. You can either select the whole account (all actions will be granted) or refine by toggling individual actions.
> 5. **(Optional) Load tools when needed.** On by default, and the toggle that puts the connection into [Advanced Tool Search](https://docs.stackone.com/optimize/advanced-tool-search.md). Leave it on for large action sets. Turn it off to hand the agent every selected action up front.
> 6. **Authorize.** Completes the connection; you can return to your client.
>
> ![StackOne authorization screen listing organizations, with a project selected inside one of them](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/oauth-consent-select-project.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=69d4694c8ea854c52ec62fc1bbe0825a)
>
> Select a project
>
> ![StackOne authorization screen showing two linked accounts, Linear and Open-Meteo, both selected, above the Load tools when needed toggle](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/oauth-consent-select-accounts.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=66ef4eb4d8bf6e5246e5f01ec959c187)
>
> Select accounts
>
> ![An expanded linked account showing individual actions with toggles, descriptions, and category tags](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/oauth-consent-select-actions.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=c86b615e0f55cd43236e38142c1ebca5)
>
> Toggle actions
>
> > [!NOTE]
> >
> > If you see a sentence where the **Load tools when needed** toggle should be, an admin has already settled it for the whole project. See [project settings](https://docs.stackone.com/optimize/advanced-tool-search.md#setting-it-for-a-whole-project).

**Connect to server** now shows **Connected**, and the discovered tools appear on the **Tools** tab.

> [!NOTE]
>
> Your connection covers tool discovery and configuration only. Glean's [documentation](https://docs.glean.com/administration/tools/connect-remote-mcp-servers-to-glean) 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](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/glean/glean-enable-tools.png?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=d343cd3b7ecf851814cc4e048165f2cd)

> [!NOTE]
>
> 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](https://docs.glean.com/administration/tools/managing-tools/tools-chat-vs-agents) and [run without user confirmation](https://docs.glean.com/administration/tools/managing-tools/run-without-user-confirmation) guides.

**6. Verify**

The server appears under **Vendor provided tools (via MCP)** with status **Enabled**.

> [accordion] Connecting with a token app instead
>
> 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](https://docs.stackone.com/ai-platforms/mcp-server.md#choosing-a-connection-method).
>
> [Create a token app](https://docs.stackone.com/ai-platforms/mcp-server.md#create-a-token-app) under **Connected Apps → Token apps**, select the Linked Accounts it covers, and copy its **MCP URL**:
>
> ```
> https://api.stackone.com/mcp?token={token}
> ```
>
> 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](https://docs.stackone.com/optimize/advanced-tool-search.md), add the `tool-mode` query parameter to the URL:
>
> ```
> https://api.stackone.com/mcp?token={token}&tool-mode=search_execute
> ```
>
> 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](https://docs.stackone.com/secure/identity-and-access/manage-team/overview).
* **Create groups.** Organize teams into [groups](https://docs.stackone.com/secure/identity-and-access/roles-and-groups/groups.md) to control which systems each team reaches.
* **Set up connectors.** Define [Connector Profiles](https://docs.stackone.com/connect/managing-connectors/connector-profiles.md) to scope provider actions for specific functions.
* **Link accounts.** Link shared company accounts, or let users link their own accounts. See [Linking Accounts](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md).

Then send users one of the following guides, depending on the product:

> [card] [Glean Assistant](https://docs.stackone.com/ai-platforms/glean/glean-assistant/organization-user-setup.md)
>
> For people using StackOne in Glean Assistant.

> [card] [Glean Agents](https://docs.stackone.com/ai-platforms/glean/glean-agents/agent-builder-setup.md)
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.