Enrichment inside your AI tools

Add SalesQL as a custom MCP server from Plugins. Developer mode is no longer needed — ChatGPT shows a risk warning for each server instead.

1. In ChatGPT on the web, open Plugins in the sidebar, click Add and choose Add custom MCP server.

   

2. Name it SalesQL, paste https://mcp.salesql.com/mcp under Connection and set Authentication to OAuth — there is no need to open Advanced OAuth settings. Tick I understand and want to continue, then click Create as a plugin.

   

3. Click Connect SalesQL. (In a Business or Enterprise workspace where an admin has already approved SalesQL, the button reads Continue to SalesQL.)

   

4. On the SalesQL consent screen, keep the permissions you want ChatGPT to use and click Connect.

   

5. In a new chat, type @ (or click +) and pick SalesQL. Pick it again whenever a follow-up needs fresh data — the selection applies to one message.

   

Works on personal accounts — Free included — and in workspaces, on ChatGPT on the web only. In a Business or Enterprise/Edu workspace, only admins and owners can add one unless an admin grants you Create plugins with MCPs. Don’t see Plugins yet? Use Settings → Apps → Advanced settings → Developer mode, then Apps → Create.

# Plugins → Add → Add custom MCP server
Name:  SalesQL
URL:   https://mcp.salesql.com/mcp
Auth:  Bearer YOUR_MCP_KEY

One command, then authorize in the browser. Keep --transport http — it is the only transport that carries OAuth — and --scope user, so SalesQL is there in every project instead of just this folder.

claude mcp add --transport http --scope user salesql https://mcp.salesql.com/mcp

1. Run the command above.
2. Type /mcp inside Claude Code, pick salesql, and choose Authenticate.

   

3. Approve the scopes in the browser tab that opens.

Already added SalesQL on claude.ai? If you sign in to Claude Code with that Claude account, the connector shows up there on its own. Tokens are stored securely and refresh by themselves; the same /mcp panel has Clear authentication when you want to disconnect.

claude mcp add --transport http --scope user salesql \
  https://mcp.salesql.com/mcp \
  --header "Authorization: Bearer YOUR_MCP_KEY"

Register the server once and sign in from the terminal. The Codex CLI, the IDE extension and the desktop app all read the same ~/.codex/config.toml, so this covers all three.

codex mcp add salesql --url https://mcp.salesql.com/mcp
codex mcp login salesql

1. Run the first command to add SalesQL to ~/.codex/config.toml.
2. Run codex mcp login salesql and approve the scopes in the browser tab that opens.
3. Start a new Codex session — the SalesQL tools are available.

Prefer clicking? In the desktop app open Settings → MCP servers, or in the IDE extension the gear menu → MCP servers; choose Add server → Streamable HTTP, paste the URL, save and restart.

[mcp_servers.salesql]
url = "https://mcp.salesql.com/mcp"
bearer_token_env_var = "SALESQL_MCP_KEY"

Point Cursor at the endpoint and let it handle the handshake — OAuth 2.1 with PKCE, registering itself as it goes.

{
  "mcpServers": {
    "salesql": {
      "url": "https://mcp.salesql.com/mcp"
    }
  }
}

1. Add the block above to ~/.cursor/mcp.json — or .cursor/mcp.json to scope it to one project.
2. Open Customize → MCPs (in Cursor before 3.9: Settings → MCP) and click Connect next to salesql.
3. Approve the scopes in the browser.

No client ID or secret to fill in: the server registers Cursor dynamically.

{
  "mcpServers": {
    "salesql": {
      "url": "https://mcp.salesql.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_MCP_KEY" }
    }
  }
}

For GitHub Copilot agent mode. VS Code notices the server wants OAuth and opens a browser to sign you in — the file holds no secret, so you can commit it.

{
  "servers": {
    "salesql": {
      "type": "http",
      "url": "https://mcp.salesql.com/mcp"
    }
  }
}

1. Save the block above as .vscode/mcp.json — or run MCP: Add Server from the Command Palette, choose HTTP and paste the URL.
2. Start salesql from MCP: List Servers, or just ask Copilot for a SalesQL tool.
3. Approve the scopes in the browser window VS Code opens. The sign-in then lives in the Accounts menu.

Because there is no key in it, this file is safe to commit — every teammate authorizes with their own SalesQL account.

{
  "servers": {
    "salesql": {
      "type": "http",
      "url": "https://mcp.salesql.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_MCP_KEY" }
    }
  }
}

Add the server with one command, then authorize once from inside the CLI. No token in your settings file.

gemini mcp add --transport http --scope user salesql https://mcp.salesql.com/mcp

1. Run the command above. It writes the server to ~/.gemini/settings.json (without --scope user, only to this project).
2. Run /mcp auth salesql inside the CLI.
3. Approve the scopes in the browser.

Gemini CLI discovers the OAuth endpoints from the server itself. Tokens are cached in ~/.gemini/mcp-oauth-tokens.json and refreshed automatically — re-run /mcp auth if they ever expire.

{
  "mcpServers": {
    "salesql": {
      "httpUrl": "https://mcp.salesql.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_MCP_KEY" }
    }
  }
}

Add SalesQL as a custom remote connector and let Perplexity discover the rest.

1. Open Plugins in the sidebar (older layout: Customize → Connectors), then Add custom → Connector → Add MCP connector, and choose Remote.
2. Name it SalesQL, paste https://mcp.salesql.com/mcp as the MCP Server URL, and set Authentication to OAuth and Transport to Streamable HTTP.
3. Tick the acknowledgement and click Add.
4. Click the SalesQL card to sign in and approve the consent screen.

Leave Client ID and Client Secret empty — the server supports dynamic registration, so Perplexity registers itself. Remote connectors need a Pro, Max or Enterprise plan; on Enterprise an admin may have to allow custom connectors first.

# Plugins → Add custom → Connector → Add MCP connector → Remote
Name:  SalesQL
URL:   https://mcp.salesql.com/mcp
Auth:  Bearer YOUR_MCP_KEY

Any client that speaks Streamable HTTP and the MCP authorization spec can connect unaided: the server publishes its own metadata and accepts dynamic client registration, so there is nothing to pre-register and no secret to exchange.

Endpoint:   https://mcp.salesql.com/mcp
Transport:  Streamable HTTP
Auth:       OAuth 2.1 — authorization code + PKCE (S256)
Discovery:  https://mcp.salesql.com/.well-known/oauth-protected-resource/mcp

Endpoint:  https://mcp.salesql.com/mcp
Header:    Authorization: Bearer YOUR_MCP_KEY