What is the MCP Server?

The Sales Layer MCP Server is a secure bridge between your Sales Layer product data and AI or automation tools that support the Model Context Protocol.

It allows compatible tools, such as AI assistants, IDEs, and workflow automation platforms, to query, analyze, and interact with your product catalog through a standardized connection. This helps teams build AI-powered product assistants, automated enrichment workflows, data validation processes, and intelligent search tools without creating a custom integration from scratch.

Before you start

Before connecting an AI client to the Sales Layer MCP Server, you need your Sales Layer Catalog Token.

1. Log in to your Sales Layer account.
2. Go to the administration area.
3. Open the API/Tokens section.
4. Copy your Catalog Token.

Server URLs

The main Sales Layer MCP Server URL is:

https://mcp.saleslayer.com

Use one of the following access profiles depending on the type of connection you need:

Authentication

The Sales Layer MCP Server uses OAuth 2.0 with PKCE. In remote clients, the Catalog Token is entered in the Sales Layer authorization window. After the token is validated, the MCP Server issues an OAuth access token for the client.

Many clients can detect the OAuth configuration automatically by using Dynamic Discovery or Dynamic Client Registration. If your client does not support automatic discovery, use the manual OAuth configuration below.

To obtain an API Key please contact Sales Layer support or your account representative, at support@saleslayer.com

Microsoft Copilot Studio

If your version of Microsoft Copilot Studio supports Dynamic Discovery, use it as the recommended configuration method.

1. In Copilot Studio, go to Tools > Add tool > Model Context Protocol.
2. Set the server name as Sales Layer MCP.
3. Set the server description as MCP Server for PIM Sales Layer.
4. Use this server URL: https://mcp.saleslayer.com/mcp.
5. In Authentication, select OAuth 2.0.
6. If available, select Dynamic Discovery.
7. Click Create.
8. When the browser window opens, enter your Sales Layer Catalog Token in the authorization screen.

If Dynamic Discovery is not available, configure OAuth manually using the values in the Authentication section of this article. The Client ID must be a stable identifier for the client, such as copilot-studio. It is not the Catalog Token.

Claude Web

1. In a Claude conversation, click the tools or connectors icon.
2. Select Add MCP Server or the equivalent option in your version.
3. Enter this URL: https://mcp.saleslayer.com/mcp.
4. Claude should detect the OAuth configuration automatically through Dynamic Client Registration.
5. When the authorization window opens, enter your Sales Layer Catalog Token.
6. Once connected, you can ask Claude questions about your Sales Layer product catalog.

Claude Desktop

Claude Desktop runs the MCP server locally, so it does not require OAuth for this setup.

1. Open the Claude Desktop configuration file.
2. On Windows, the file is located at %APPDATA%\Claude\claude_desktop_config.json.
3. On macOS, the file is located at ~/Library/Application Support/Claude/claude_desktop_config.json.
4. Add the following configuration.

{
  "mcpServers": {
    "sales-layer": {
      "command": "npx",
      "args": ["--yes", "@saleslayer/mcp-server@latest"],
      "env": {
        "CATALOG_TOKEN": "your_token_here"
      }
    }
  }
}

1. Replace your_token_here with your real Sales Layer Catalog Token.
2. Restart Claude Desktop.
3. To verify the connection, ask Claude: What Sales Layer tools do you have available?

ChatGPT

MCP support in ChatGPT may vary depending on the version and plan.

1. Open the ChatGPT settings.
2. Look for the option to add MCP Servers or External Tools.
3. Add a new server with this URL: https://mcp.saleslayer.com/mcp.
4. Select OAuth 2.0 as the authentication method.
5. If supported, ChatGPT should detect the configuration automatically through Dynamic Client Registration.
6. When the authorization window opens, enter your Sales Layer Catalog Token.

Cursor IDE

Cursor supports MCP with automatic OAuth authentication.

1. Open Settings > Tools & MCP.
2. Click Add new MCP server.
3. Select Streamable HTTP.
4. Enter this URL: https://mcp.saleslayer.com/mcp.
5. Click Connect.
6. When Cursor opens the browser, complete the OAuth flow by entering your Sales Layer Catalog Token.

You can also configure Cursor from the .cursor/mcp.json file in your project:

{
  "mcpServers": {
    "sales-layer": {
      "url": "https://mcp.saleslayer.com/mcp"
    }
  }
}

When the server is activated, Cursor starts the OAuth flow automatically.

VS Code with GitHub Copilot

VS Code supports MCP through GitHub Copilot in compatible versions.

1. Open the Command Palette using Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows.
2. Run MCP: Add Server....
3. Select HTTP.
4. Enter this URL: https://mcp.saleslayer.com/mcp.
5. Give the server a name, for example sales-layer.
6. Choose whether to save the configuration in User Settings or in the current Workspace.

You can also create or edit the .vscode/mcp.json file in your project:

{
  "servers": {
    "sales-layer": {
      "type": "http",
      "url": "https://mcp.saleslayer.com/mcp"
    }
  }
}

To use the connection, open Copilot Chat and activate Agent mode. VS Code should detect the server and complete the OAuth flow automatically. Enter your Sales Layer Catalog Token when the authorization form appears.

Windsurf IDE

Windsurf supports MCP through its Cascade agent.

1. Open Windsurf Settings.
2. Go to Cascade > MCP Servers.
3. Click Add Custom Server +.
4. Add the following configuration.

{
  "mcpServers": {
    "sales-layer": {
      "serverUrl": "https://mcp.saleslayer.com/mcp"
    }
  }
}

You can also edit the Windsurf MCP configuration file directly:

• macOS: ~/.codeium/windsurf/mcp_config.json
• Windows: %APPDATA%\Codeium\windsurf\mcp_config.json

If Windsurf does not support native OAuth for remote servers, you can use the mcp-remote proxy:

{
  "mcpServers": {
    "sales-layer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.saleslayer.com/mcp"]
    }
  }
}

This opens the browser for authentication and manages the tokens automatically.

n8n

For n8n workflows, the recommended option is to use the MCP Client Tool or MCP Client with OAuth 2.0.

1. In your workflow, use MCP Client Tool if you want to expose tools to an AI Agent.
2. Use MCP Client if you want to run an MCP tool as a normal workflow step.
3. Use this URL: https://mcp.saleslayer.com/mcp.
4. In some n8n versions, this field may appear as SSE Endpoint or MCP Endpoint URL.
5. In Authentication, select OAuth2.
6. If your version supports Discovery or Dynamic Client Registration, enable it.
7. If n8n asks for a Registration URL, use https://mcp.saleslayer.com/oauth/register.
8. When the browser window opens, enter your Sales Layer Catalog Token.

If your n8n version does not support OAuth2 correctly with MCP, use the Sales Layer REST API directly instead of the MCP Server.

This direct REST API option does not use the MCP protocol, so MCP tools will not be available to an AI Agent. It is useful for automation workflows that only need direct API access.

Google Gemini and other MCP clients

Before configuring Google Gemini, confirm that your version supports MCP. If it supports MCP with OAuth, add the Sales Layer MCP Server with this URL:

https://mcp.saleslayer.com/mcp

Use OAuth 2.0 with Dynamic Discovery where available, then authenticate with your Sales Layer Catalog Token.

For any other MCP-compatible client, use the same MCP URL and OAuth 2.0 configuration. If the client supports Dynamic Client Registration, let the client discover the configuration automatically. If not, use the manual OAuth values listed in the Authentication section of this article.

Troubleshooting

Best practices

Use Dynamic Discovery or Dynamic Client Registration whenever your client supports it, as this reduces the risk of configuration errors. 

Keep your Catalog Token secure and only enter it in the Sales Layer authorization screen. 

Do not paste it as an API key or Bearer token in remote MCP clients.

For automation workflows that do not need MCP tools or an AI Agent, consider using the Sales Layer REST API directly with the X-API-KEY header.