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

# ChatGPT - Make StackOne Available

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

![An IT admin adds StackOne to the ChatGPT workspace, bringing Linked Accounts from many providers. Each user then connects with their own accounts: an HR manager uses ChatGPT with Workday, Greenhouse and BambooHR, and a sales manager uses ChatGPT with Salesforce, HubSpot and Gmail.](https://mintcdn.com/stackone-60/RgaE_4ZxFuvAQ6gS/images/ai-platforms/openai/admin-setup.svg?fit=max\&auto=format\&n=RgaE_4ZxFuvAQ6gS\&q=85\&s=9369b1fdbcbf1105622e8c25896c5af8)

Make the StackOne connector available to everyone in your ChatGPT Business, Enterprise or Edu workspace. 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

In ChatGPT, a workspace policy may need to allow custom MCP servers for your role first.

You sign in to StackOne yourself during setup, so ChatGPT 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 your workspace

**1. Add the custom MCP server**

Add the server in a browser. The desktop app picks it up from there once it exists.

1. Go to [ChatGPT Plugins](https://chatgpt.com/plugins).

2. Select **Add**, then **Add custom MCP server**.

3. Enter a name and description, for example `StackOne`.

4. Under **Connection**, enter the MCP server URL:

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

5. Set authentication to **OAuth** and leave **Advanced OAuth settings** as discovered. ChatGPT discovers the endpoints and registers itself, so there is no client ID or secret to enter. No `mcp-remote` wrapper needed. If ChatGPT asks you to confirm that the provider issues refresh tokens, confirm it.

6. Review the risk warning and select **I understand and want to continue**.

7. Select **Create as a plugin**.

8. Select **Connect StackOne** to start the sign-in.

If **Add custom MCP server** is missing from the menu, a workspace policy is blocking it for your role.

**2. Approve the consent screen**

ChatGPT 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).

Back in ChatGPT, review the tools it discovered, then install the plugin.

**3. Publish it to the workspace**

The plugin is yours as soon as it is installed. Publishing makes it available to everyone else.

> [tab] Business
>
> Open **Workspace Settings → Apps → Drafts** and click **Publish**, reviewing the safety warnings for any write actions.
>
> Published apps show in the workspace's approved connectors list, labeled **custom**. They cannot be edited afterwards, so changing the tools or metadata means creating and publishing the app again.

> [tab] Enterprise and Edu
>
> Open **Workspace Settings → Apps → Drafts** and click **Publish**.
>
> In the dialog that follows, **Configure Actions** selects which actions the app may run, and **Configure Access** limits it to specific groups. Both stay editable after publishing, from the ellipsis menu next to the app under **Workspace Settings → Apps**.

## Roll it out

StackOne is now available for your users in ChatGPT. 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 this guide:

> [card] [ChatGPT Organization User Setup](https://docs.stackone.com/ai-platforms/openai/chatgpt/organization-user-setup.md)
>
> For people in your workspace connecting StackOne in ChatGPT.

## Keep the published tool list current

A published app works from a snapshot of the tools StackOne exposed when it was added. To pick up changes, refresh it from the ellipsis menu next to the app under **Workspace Settings → Apps**, turn on any new actions, and publish it again.

[Advanced Tool Search](https://docs.stackone.com/optimize/advanced-tool-search.md) avoids refreshes. It replaces the per-action tool list with two stable tools, Search and Execute, so any changes to the available actions are respected without a refresh.


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