Overview

The Sales Layer MCP Server can be used with any client that supports the Model Context Protocol and can connect to remote MCP servers securely.

This article explains the general configuration values to use when connecting Sales Layer to MCP-compatible clients that do not have a dedicated Sales Layer setup guide.

Before you start

Before connecting another MCP-compatible client to Sales Layer, make sure you have:

• An MCP-compatible client that supports remote MCP servers or local MCP server configuration.
• Support for OAuth 2.0 with PKCE if you are using the remote Sales Layer MCP Server.
• Access to the Sales Layer catalog you want to use.
• Your Sales Layer Catalog Token.
• Permission from your organization to connect external AI tools to your product catalog data.

At the moment, the Catalog Token is not obtained from an API/Tokens section inside the Sales Layer PIM. To get it, contact Sales Layer Support or your Sales Layer account representative.

Choose the connection type

MCP clients can connect to Sales Layer in different ways depending on what the client supports.

If your client supports remote MCP with OAuth 2.0 and PKCE, use the remote MCP Server option. If it does not, check whether a local bridge or local package is supported.

Choose the access mode

Use the access mode that matches what the MCP client should be allowed to do with your Sales Layer catalog.

For most first-time setups, start with Read-only. Use Full access only for trusted workflows where the AI client is expected to modify catalog data.

Option 1: Connect using a remote MCP Server URL

Use this option when the client supports remote MCP servers and OAuth 2.0 with PKCE.

1. Open your MCP-compatible client.
2. Go to the section for tools, connectors, extensions, agents, or MCP servers.
3. Add a new MCP server.
4. Enter a clear server name, for example Sales Layer MCP.
5. Enter the Sales Layer MCP Server URL.
6. Select OAuth 2.0 if the client asks for an authentication method.
7. Use Dynamic discovery if the client supports it.
8. Save or connect the server.

Use this URL for the standard remote setup:

https://mcp.saleslayer.com/mcp

Manual OAuth values

If the client does not support Dynamic discovery and asks for manual OAuth values, use the following configuration:

Option 2: Connect through a local bridge

Some MCP clients support local command-based servers but do not support remote MCP OAuth directly. In this case, your technical team may use a local bridge such as mcp-remote, if allowed by your organization.

Example configuration:

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

This setup starts a local MCP process and connects it to the remote Sales Layer MCP Server. It usually requires Node.js, npx, and permission to run local commands on the computer.

Option 3: Use a local MCP package

Some clients support local MCP packages. In this setup, the MCP server runs locally and the Catalog Token is entered during package setup.

Use this option only when Sales Layer provides a local package for the client or when the client supports compatible MCP package installation.

1. Download the Sales Layer local MCP package from the Sales Layer MCP page or from the location provided by Sales Layer Support.
2. Install the package in your MCP-compatible client.
3. Enter your Sales Layer Catalog Token during the package configuration step.
4. Restart the client if required.
5. Test the connection with a simple prompt.

Complete the Sales Layer authorization flow

For remote MCP connections, the client should open the Sales Layer authorization screen in your browser.

1. Wait for the Sales Layer authorization screen to open.
2. Select the access profile if the screen asks you to choose one.
3. Enter your Sales Layer Catalog Token.
4. Validate the token and continue.
5. Return to your MCP client when the authorization flow is complete.

Test the connection

After the MCP Server is connected, test the connection before using it for real catalog work.

Start with:

What Sales Layer tools are available?

Then test with a catalog-related prompt:

Show me a summary of my Sales Layer catalog.

If the connection is working, the client should be able to call the Sales Layer MCP tools and return information from your catalog.

Example prompts

Once the connection is ready, you can ask:

• Show me the available Sales Layer tools.
• Search for products with missing descriptions.
• Summarize the catalog structure.
• Check product data quality for a specific category.
• Find items with incomplete technical attributes.

If you are using read-only access, the client can query and analyze Sales Layer data, but it cannot create or update records.

When to use the REST API instead

Use the Sales Layer REST API directly when your workflow does not need MCP tools or when the client cannot complete the required OAuth flow for remote MCP.

For direct REST API calls, use the X-API-KEY header with your Sales Layer Catalog Token:

X-API-KEY: your_catalog_token

For example, API 2.0 REST catalog queries use URLs such as:

https://api2.saleslayer.com/rest/Catalog/Products

This is not an MCP connection. It is useful for fixed, predictable automations where the workflow already knows which endpoint to call.

Troubleshooting

What to send to Sales Layer Support

If the issue continues, contact Sales Layer Support and include:

• The MCP client name and version.
• The connection type you are using: remote MCP, local bridge, local package, or REST API.
• The server URL you configured.
• The authentication method selected in the client.
• The exact error message shown by the client.
• A screenshot of the error, with sensitive token values hidden.
• Whether the Sales Layer authorization screen opened.
• Whether you selected read-only or full access.

Never send your full Catalog Token in a screenshot, ticket, email, or chat conversation.

Best practices

Use a client-specific Sales Layer article when one is available. Generic MCP setup should be used only when the client does not have a dedicated guide.

Start with read-only access when the client only needs to query or analyze catalog data. Use full access only for controlled workflows that are expected to modify data.

Use Dynamic discovery when the client supports it. If manual OAuth setup is required, carefully review each endpoint and confirm that PKCE with S256 is supported.

Keep your Catalog Token secure. Do not paste it into configuration files, screenshots, support tickets, public templates, or shared repositories.

If your client cannot support remote MCP authentication, do not force the setup by sending the Catalog Token as a bearer token. Use a compatible client, a local bridge approved by your organization, or the Sales Layer REST API directly.