Claude - Make StackOne Available

An IT admin adds StackOne to the Claude organization, bringing Linked Accounts from many providers. Each user then connects with their own accounts: an HR manager uses Claude Chat with Workday, Greenhouse and BambooHR, and a developer uses Claude Code with GitHub, Linear and Slack.

Make the StackOne connector available to everyone in your Claude Team or Enterprise organization. Each person then signs in with their own StackOne login and reaches only the systems they’ve been given access to in StackOne. It also reaches developers signed in to Claude Code with their Claude account.

Add StackOne to your organization

Only a Claude Owner or Primary Owner can add it. On Enterprise, a custom role that includes Manage access to Libraries also works.

Add a custom connector

In Claude, go to Organization settings → Connectors.
Select Add, then Custom. If Claude asks for the connector type, choose Web.

Enter the name and URL

Enter StackOne as the name and https://mcp.stackone.com/mcp as the URL, then click Continue. Users find the connector by this name under Customize → Connectors.

Choose how Claude signs in

Under OAuth client, choose Use Claude’s published identity or Register automatically. Claude identifies itself to StackOne, so there’s no client ID or secret to enter.

Use your own OAuth client instead

To have Claude sign in through a client your StackOne project owns:

Create the client by following Clients requiring Client ID and Secret, with the Claude preset.
Under OAuth client, choose Use your own OAuth client. If the dialog shows everything on one screen, it’s under Advanced.
Enter the client ID and secret.

You can’t change these sign-in settings once the connector is added. Changing them means removing the connector and adding it again, and then everyone connects again.

Add

Click Add.

For developers signing in to Claude Code with an API key, Amazon Bedrock or Google Cloud

Claude Code does not load Claude connectors when developers sign in with an API key, Amazon Bedrock or Google Cloud. Add StackOne in Claude Code instead.To share it through a project, add the server with project scope, which writes it to .mcp.json at the project root:

claude mcp add --transport http --scope project stackone https://mcp.stackone.com/mcp

A --scope project entry is safe to commit, because the URL carries no access of its own. Each teammate authenticates as themselves and gets their own Linked Accounts.To give StackOne to every developer in the organization, list it under managedMcpServers in managed settings. Developers receive it in addition to the servers they add themselves:

{
  "managedMcpServers": {
    "stackone": {
      "type": "http",
      "url": "https://mcp.stackone.com/mcp"
    }
  }
}

Claude Code loads an entry only when its type is http or sse and its url starts with https://. Claude Code versions earlier than v2.1.259 ignore the setting. See Managed MCP configuration in the Claude Code docs for where to deploy managed settings.

Roll it out

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

Claude Chat & Cowork

For people using Claude on the web, in the desktop app or in Cowork.

Claude Code

For developers using Claude Code in the terminal or their editor.

Developers who add StackOne to their own setup follow Personal Setup instead.