Claude Desktop & Web

Overview

Claude connects to remote MCP servers as custom connectors, running the OAuth flow itself, with no config file and no mcp-remote wrapper. A connector is added once against your account and is then available in Claude on desktop, web and mobile.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans, with Free limited to one. See Anthropic’s guide to custom connectors for the current flow.

Prerequisites

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.

Setup

Add the connector

How you add the connector depends on your Claude plan. On Pro and Max you add it yourself, and on Team and Enterprise an Owner adds it for everyone.

Pro and Max
Team and Enterprise

Go to Customize → Connectors.
Open the Add dropdown and select Add custom connector.
Set the name (e.g. StackOne) and the Remote MCP Server URL:
https://mcp.stackone.com/mcp
Leave the OAuth client ID and secret fields empty (Claude discovers the endpoints and registers itself).
Click Add.

Go to Organization settings → Connectors.
Click Add, hover over Custom, then select Web.
Set the Remote MCP Server URL:
https://mcp.stackone.com/mcp
Leave the OAuth credentials under Advanced settings empty (Claude discovers the endpoints and registers itself).
Click Add.

Connect

Under Customize → Connectors, click Connect on the StackOne connector.

Approve the consent screen

Claude opens StackOne in your browser.Sign in, pick the project and the linked accounts the connector should reach, then Authorize.

Verify connection

StackOne appears under Customize → Connectors, where you can review each tool and set whether it runs automatically or asks first:

Claude Desktop Connectors page showing tool permissions with options to enable or require approval for each tool

Then try prompts like:

What StackOne tools are available?

Search recent calls in Gong

One grant covers every account you approved, so a single connector is usually all you need. To change which accounts or actions it can reach, disconnect the current connector and then run the flow again; to revoke it, use Connected Apps in the StackOne dashboard.

Connecting with a session token instead

A session token URL carries its own credential, so it covers the cases OAuth can’t: 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.From the StackOne dashboard, go to Connectors, open a connector, then click Use in Agent.

Pick a linked account.
Set the expiry (one year by default).
Select HTTPS MCP and copy the URL. It should be in the format of:
https://api.stackone.com/mcp?token={session_token}

This URL covers one linked account, 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:

https://api.stackone.com/mcp?token={session_token}&tool-mode=search_execute

A token URL is not a remote OAuth connector, so it goes through the mcp-remote package in claude_desktop_config.json. Open it from Settings → Developer → Edit Config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gsheets": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?token={session_token}"
      ]
    }
  }
}

Restart Claude Desktop to load it. Servers added this way show under Settings → Developer with a green “running” badge; if you see “failed”, click Open Logs Folder.

Multiple accounts example

For multiple linked accounts, add an entry for each. Get each token from the dashboard by selecting the relevant account.

Claude Desktop Connectors page showing multiple MCP servers configured for different integrations

{
  "mcpServers": {
    "gsheets": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?token={google_sheets_session_token}"
      ]
    },
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?token={slack_session_token}"
      ]
    }
  }
}

Alternative: manual API key setup

If you prefer to use your API key and account ID directly, encode your API key first:

macOS / Linux
Windows (PowerShell)
Windows (Command Prompt)

echo -n "{stackone_api_key}:" | base64

[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("{stackone_api_key}:"))

powershell -Command "[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes(\"{stackone_api_key}:\"))"

Terminal showing base64 encoding command and output

Then add to your config:

{
  "mcpServers": {
    "gsheets": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id={account_id}",
        "--header",
        "Authorization: Basic {base64_encoded_api_key}"
      ]
    }
  }
}

Programmatic integration

For programmatic integration with Anthropic’s Claude API, see the Anthropic SDK Framework Guide.

Optimize and secure

With your agent connected, use StackOne’s platform features to optimize performance and secure every call.

Advanced Tool Search

Reduce context and save tokens.

Deep Query

Search synced records for a fraction of the tokens.

Defender

Block prompt injections before they reach your agent.

​Overview

​Prerequisites

​Setup

​Programmatic integration

​Optimize and secure

Advanced Tool Search

Deep Query

Defender

Overview

Prerequisites

Setup

Programmatic integration

Optimize and secure