ChatGPT - Make StackOne Available

Before you start

• 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 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.
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:
   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 the connector should reach, then Authorize.

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

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.

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.

• Business
• Enterprise and Edu

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.

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

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

Keep the published tool list current